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

AS212636 · 

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

Warning: AS212636 (s2bnet S2B-NET SARL) announces 2 IPv4 and 0 IPv6 prefixes. 4 warnings

AS pageAS212636
Holders2bnet S2B-NET SARL
AllocationRIPE NCC, France (FR), allocated 2020-09-18
Prefixes (IPv4 / IPv6)2 / 0
RPKI valid50% (1 / 2)
Upstreams and peers2

What to fix

  1. Warning

    No IPv6 prefixes announced.

    Networks without IPv6 force their users through NAT64 or leave them unreachable from IPv6-only networks.

    Fix: Get an IPv6 allocation from your RIR (usually free with your IPv4 membership) and announce it.

    Open in ASN & BGP prefix lookup

  2. Warning

    1 of 2 announced prefixes have no ROA (RPKI not found): 149.100.136.0/24.

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

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

    149.100.136.0/24 AS212636 max-length /24

    Open in RPKI / ROA validator Guide

  3. Warning

    1 of 2 announced prefixes have no IRR route object: 193.23.52.0/24.

    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 AS212636 in your RIR’s IRR database (or RADB).

    route: 193.23.52.0/24
origin: AS212636

    Open in ASN & BGP prefix lookup

  4. Warning

    PeeringDB did not answer: HTTP 404

    Fix: Try again in a minute.

    Open in PeeringDB lookup

Checks

Routing and RPKI No IPv6 prefixes announced.
  • Pass: AS212636 announces 2 IPv4 and 0 IPv6 prefixes.
  • Warning: No IPv6 prefixes announced.
  • Warning: 1 of 2 announced prefixes have no ROA (RPKI not found): 149.100.136.0/24.
  • Info: 1 of 2 announced prefixes are RPKI valid.
  • Warning: 1 of 2 announced prefixes have no IRR route object: 193.23.52.0/24.
  • Info: 2 upstreams and peers, 0 downstream networks seen.
Holders2bnet S2B-NET SARL
IPv4 prefixes2
IPv6 prefixes0
RPKI1 valid · 1 not found
Without IRR route object1
Downstream networks0
Routes to fix
PrefixRPKI
149.100.136.0/24 No ROA

Upstreams and peers seen to the left 2

AS1299 Arelion (Twelve99) AS174 Cogent Communications, Inc.

Announced prefixes 2

149.100.136.0/24 193.23.52.0/24

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.
Names2bnet
HandleAS212636
RangeAS212636
Statusactive
Registered2020-09-18T09:56:58Z
Last changed2020-09-18T09:56:58Z
Abuse contactabuse@s2b-net.fr
Allocation
Registry (RIR)RIPE NCC
CountryFrance (FR)
Delegated on2020-09-18
StatusAllocated
Delegated rangeAS212636

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

Contacts
RoleNameEmail
registrant mnt-fr-s2b-net-1
registrant S2B-NET SARL
registrant RIPE-NCC-END-MNT
abuse Abuse-C Role abuse@s2b-net.fr

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