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

AS200978 ·

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

Warning: AS200978 (BIT-SERV Biesterfeld SE) announces 2 IPv4 and 1 IPv6 prefixes. 1 warning

AS pageAS200978
HolderBIT-SERV Biesterfeld SE
AllocationRIPE NCC, Germany (DE), allocated 2015-02-27
Prefixes (IPv4 / IPv6)2 / 1
RPKI valid100% (3 / 3)
Upstreams and peers2

What to fix

  1. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI AS200978 announces 2 IPv4 and 1 IPv6 prefixes.
  • Pass: AS200978 announces 2 IPv4 and 1 IPv6 prefixes.
  • Pass: All 3 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
HolderBIT-SERV Biesterfeld SE
IPv4 prefixes2
IPv6 prefixes1
RPKI3 valid
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.
NameBIT-SERV
HandleAS200978
RangeAS200978
Statusactive
Registered2015-02-27T09:51:29Z
Last changed2018-09-04T11:33:38Z
Abuse contactripe-msgs@bit-serv.de
Allocation
Registry (RIR)RIPE NCC
CountryGermany (DE)
Delegated on2015-02-27
StatusAllocated
Delegated rangeAS200978

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

Contacts
RoleNameEmail
registrant BIT-SERV-GMBH-MNT
registrant Biesterfeld SE
registrant RIPE-NCC-END-MNT
abuse BIT-SERV Contact ripe-msgs@bit-serv.de

Source: https://rdap.db.ripe.net/autnum/200978. 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