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

AS33846 ·

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

Warning: AS33846 (DATAPORT-AS Dataport AoR) announces 5 IPv4 and 23 IPv6 prefixes. 3 warnings

AS pageAS33846
HolderDATAPORT-AS Dataport AoR
AllocationRIPE NCC, Germany (DE), allocated 2004-08-17
Prefixes (IPv4 / IPv6)5 / 23
RPKI valid11% (3 / 28)
Upstreams and peers2

What to fix

  1. Warning

    10 of 28 announced prefixes have no ROA (RPKI not found): 193.17.28.0/22, 193.168.236.0/22, 2a02:1002:d200::/40, 2a02:1002:da20::/48, 2a02:1002:da21::/48 (+5).

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

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

    193.17.28.0/22 AS33846 max-length /22
    193.168.236.0/22 AS33846 max-length /22
    2a02:1002:d200::/40 AS33846 max-length /40
    2a02:1002:da20::/48 AS33846 max-length /48
    2a02:1002:da21::/48 AS33846 max-length /48
    2a02:1002:da28::/48 AS33846 max-length /48
    2a02:1002:da29::/48 AS33846 max-length /48
    2a02:1002:da38::/48 AS33846 max-length /48
    2a02:1002:da40::/48 AS33846 max-length /48
    2a02:1002:da41::/48 AS33846 max-length /48

    Open in RPKI / ROA validator Guide

  2. Warning

    23 of 28 announced prefixes have no IRR route object: 2a02:1002:d200::/40, 2a02:1002:da41::/48, 2a02:1002:da40::/48, 2a02:1002:da21::/48, 2a02:1002:da80::/48 (+18).

    Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.

    Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS33846 in your RIR’s IRR database (or RADB).

    route6: 2a02:1002:d200::/40
    origin: AS33846
    
    route6: 2a02:1002:da41::/48
    origin: AS33846
    
    route6: 2a02:1002:da40::/48
    origin: AS33846

    Open in ASN & BGP prefix lookup

  3. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI 10 of 28 announced prefixes have no ROA (RPKI not found): 193.17.28.0/22, 193.168.236.0/22, 2a02:1002:d200::/40, 2a02:1002:da20::/48, 2a02:1002:da21::/48 (+5).
  • Pass: AS33846 announces 5 IPv4 and 23 IPv6 prefixes.
  • Warning: 10 of 28 announced prefixes have no ROA (RPKI not found): 193.17.28.0/22, 193.168.236.0/22, 2a02:1002:d200::/40, 2a02:1002:da20::/48, 2a02:1002:da21::/48 (+5).
  • Info: 3 of 28 announced prefixes are RPKI valid.
  • Info: The RPKI state of 15 prefixes was not looked up (no ROA of AS33846 covers them; only the first 10 are checked).
  • Warning: 23 of 28 announced prefixes have no IRR route object: 2a02:1002:d200::/40, 2a02:1002:da41::/48, 2a02:1002:da40::/48, 2a02:1002:da21::/48, 2a02:1002:da80::/48 (+18).
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderDATAPORT-AS Dataport AoR
IPv4 prefixes5
IPv6 prefixes23
RPKI3 valid · 10 not found · 15 not looked up
Without IRR route object23
Downstream networks0

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.
NameDATAPORT-AS
HandleAS33846
RangeAS33846
Statusactive
Registered2004-08-17T09:59:03Z
Last changed2020-12-22T11:08:53Z
Abuse contactSubLIR-HH-SH@dataport.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2004-08-17
StatusAllocated
Delegated rangeAS33846

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

Contacts
RoleNameEmail
registrant Dataport AoR
registrant RIPE-NCC-END-MNT
registrant TNG-MNT
abuse Abuse-C Role SubLIR-HH-SH@dataport.de

Source: https://rdap.db.ripe.net/autnum/33846. 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 PeeringDB did not answer: HTTP 404
  • Warning: PeeringDB did not answer: HTTP 404

Source: PeeringDB. Results are cached for an hour.

Open in PeeringDB lookup