bgpreport

Network · data from 2026-11-12

AS3763 AS-BELD-1 - BELD

Registry name: AS-BELD-1 - BELD, US · not in PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
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
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS3763, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS3763, 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:808:8000::/40 No ROA None 631 99% 68
24.233.94.0/24 Valid RIR databaseARIN 670 100% 68

AS-SET

AS3763 isn't in PeeringDB, where networks name their 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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2602:808:8000::/40No ROA covers it. Add a ROA for AS3763, maxLength 40.631 of 636
Route object: none2602:808:8000::/40No route object for it. Add a route object with origin AS3763 in the RIR database for the space.631 of 636

Route objects not announced

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

24.233.64.0/19ARINValid

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.