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

AS201330 ·

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

Warning: AS201330 (SolidBE SolidBE BV) announces 1 IPv4 and 1 IPv6 prefixes. 1 warning

AS pageAS201330
HolderSolidBE SolidBE BV
AllocationRIPE NCC, Netherlands (NL), allocated 2014-11-21
Prefixes (IPv4 / IPv6)1 / 1
RPKI valid100% (2 / 2)
Upstreams and peers5

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 AS201330 announces 1 IPv4 and 1 IPv6 prefixes.
  • Pass: AS201330 announces 1 IPv4 and 1 IPv6 prefixes.
  • Pass: All 2 announced prefixes are RPKI valid.
  • Pass: Every announced prefix has an IRR route object.
  • Info: 5 upstreams and peers, 0 downstream networks seen.
HolderSolidBE SolidBE BV
IPv4 prefixes1
IPv6 prefixes1
RPKI2 valid
Downstream networks0

Announced prefixes 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.
NameSolidBE
HandleAS201330
RangeAS201330
Statusactive
Registered2014-11-21T14:03:56Z
Last changed2018-09-04T11:30:50Z
Abuse contactabuse@solidbe.nl
Allocation
Registry (RIR)RIPE NCC
CountryNetherlands (NL)
Delegated on2014-11-21
StatusAllocated
Delegated rangeAS201330

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

Contacts
RoleNameEmail
registrant SolidBE BV
registrant RIPE-NCC-END-MNT
registrant SOLIDBE-NOC-MNT
abuse SolidBE Abuse mailbox abuse@solidbe.nl

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