Skip to content
thenetworkery

Network report

Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.

IP address, prefix or AS number

AS25384 ·

curl -s "https://thenetworkery.com/api/v1/network-report?query=AS25384"
JSON Docs

Problem: AS25384 (DMDATA-AS) announces 17 IPv4 and 1 IPv6 prefixes. 1 problem · 3 warnings

AS pageAS25384
HolderDMDATA-AS Kyndryl Danmark ApS
AllocationRIPE NCC, Denmark (DK), allocated 2002-11-07
Prefixes (IPv4 / IPv6)17 / 1
RPKI valid61% (11 / 18)
Upstreams and peers2
Peering policyOpen

What to fix

  1. Problem

    1 of 18 announced prefixes are RPKI invalid: 92.60.154.0/24.

    A ROA covers them but does not allow this origin or prefix length, so networks that filter (most large ones do) drop these routes.

    Fix: Fix the ROAs (origin AS and max length) at your RIR, or stop announcing the routes.

    Open in RPKI / ROA validator Guide

  2. Warning

    6 of 18 announced prefixes have no ROA (RPKI not found): 193.162.1.0/24, 193.162.8.0/24, 193.162.9.0/24, 193.162.10.0/24, 193.162.11.0/24 (+1).

    Without a ROA, networks cannot tell your routes from a hijack.

    Fix: Create a ROA for each at your RIR portal, with origin AS25384 and a max length equal to the prefix length:

    193.162.1.0/24 AS25384 max-length /24
    193.162.8.0/24 AS25384 max-length /24
    193.162.9.0/24 AS25384 max-length /24
    193.162.10.0/24 AS25384 max-length /24
    193.162.11.0/24 AS25384 max-length /24
    193.162.12.0/24 AS25384 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    No IRR as-set is listed.

    Peers and route servers build prefix filters from the as-set. Without one they fall back to the AS number alone, which breaks as soon as you have customers.

    Fix: Create an as-set in your RIR’s IRR database and add it to your PeeringDB record.

    Open in PeeringDB lookup

  4. Warning

    No public NOC, policy or technical contact.

    Other networks use these addresses to set up peering and to reach you during an incident.

    Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.

    Open in PeeringDB lookup

Checks

Routing and RPKI 1 of 18 announced prefixes are RPKI invalid: 92.60.154.0/24.
  • Pass: AS25384 announces 17 IPv4 and 1 IPv6 prefixes.
  • Problem: 1 of 18 announced prefixes are RPKI invalid: 92.60.154.0/24.
  • Warning: 6 of 18 announced prefixes have no ROA (RPKI not found): 193.162.1.0/24, 193.162.8.0/24, 193.162.9.0/24, 193.162.10.0/24, 193.162.11.0/24 (+1).
  • Info: 11 of 18 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 2 downstream networks seen.
HolderDMDATA-AS Kyndryl Danmark ApS
IPv4 prefixes17
IPv6 prefixes1
RPKI11 valid · 1 invalid · 6 not found
Downstream networks2
Routes to fix
PrefixRPKI
92.60.154.0/24 RPKI invalid
193.162.1.0/24 No ROA
193.162.8.0/24 No ROA
193.162.9.0/24 No ROA
193.162.10.0/24 No ROA
193.162.11.0/24 No ROA
193.162.12.0/24 No ROA

Upstreams and peers seen to the left 2

Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru

Open in ASN & BGP prefix lookup
Registration Found at rdap.db.ripe.net.
  • Pass: Found at rdap.db.ripe.net.
NameDMDATA-AS
HandleAS25384
RangeAS25384
Statusactive
Registered2002-11-07T14:05:14Z
Last changed2024-04-04T12:48:40Z
Abuse contactnam.nordics@kyndryl.com
Allocation
Registry (RIR)RIPE NCC
CountryDenmark (DK)
Delegated on2002-11-07
StatusAllocated
Delegated rangeAS25384

Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.

Contacts
RoleNameEmail
registrant AS25384-MNT
registrant Kyndryl Danmark ApS
registrant RIPE-NCC-END-MNT
abuse AS25384 abuse role nam.nordics@kyndryl.com

Source: https://rdap.db.ripe.net/autnum/25384. Registration data from rdap.db.ripe.net, shown under its terms of use (terms): not for marketing or bulk collection. Personal contacts in this registry are not shown.

Open in WHOIS / RDAP lookup
PeeringDB No IRR as-set is listed.
  • Pass: AS25384 is in PeeringDB as IBM Denmark.
  • Info: Peering policy: Open.
  • Info: No internet exchange ports are listed.
  • Warning: No IRR as-set is listed.
  • Warning: No public NOC, policy or technical contact.
  • Info: The record was last updated 2022-07-27.
NetworkIBM Denmark (DMdata, IBM SDC DK)
AS numberAS25384
TypeNSP, Regional
Prefixes (IPv4 / IPv6)20 / 1
Traffic100-1000Mbps, Mostly Inbound
Peering policyOpen
LocationsNot Required
Ratio requiredNo
ContractsNot Required
Last updated2022-07-27

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup