bgpreport

Network · data from 2026-11-12

AS53837 ServedBy the Net

Registry name: SBDN-AS - ServedBy the Net, LLC., US · PeeringDB

0IPv4 routes
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS53837, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53837, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

2602:fffc::/32 No ROA None 1 0%low visibility 1

AS-SET

AS53837's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 8 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2602:fffc::/32No ROA covers it. Add a ROA for AS53837, maxLength 32.1 of 636
Route object: none2602:fffc::/32No route object for it. Add a route object with origin AS53837 in the RIR database for the space.1 of 636

Route objects not announced

Route objects with origin AS53837 whose prefix no peer sees AS53837 announce. Many are kept on purpose (backup routes, space announced only in some places).

162.223.40.0/22ARIN, NTTCOM, RADBNo ROA
162.251.48.0/21ARIN, NTTCOM, RADBNo ROA
192.48.84.0/22ARIN, NTTCOM, RADBNo ROA
204.124.88.0/22ARIN, NTTCOMNo ROA
2602:fffc::/36NTTCOMNo ROA
2607:f060:b008::/48ARINInvalid: origin

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.