bgpreport

Network · data from 2026-11-12

AS62681 ACME-WIDGET - Acme Widget LP

Registry name: ACME-WIDGET - Acme Widget LP, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62681, 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.
2620:3b:4000::/48 Valid None 636 100% 67
192.206.32.0/24 Valid RIR databaseARIN 673 100% 67
192.206.33.0/24 Valid RIR databaseARIN 673 100% 67

AS-SET

AS62681 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 5 are in fix.csv.

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2620:3b:4000::/48No route object for it. Add a route object with origin AS62681 in the RIR database for the space.636 of 636

Route objects not announced

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

192.206.32.0/23ARINValid
192.206.34.0/24ARINNo ROA
2620:3b:4000:1000::/56ARINValid
2620:3b:4000:10f0::/64ARINValid

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.