bgpreport

Network · data from 2026-11-12

AS401770 OMNIVERY-US - Omnivery

Registry name: OMNIVERY-US - Omnivery, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401770, 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.
103.65.228.0/24 Valid RIR databaseARIN 668 99% 67

AS-SET

AS401770 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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

103.65.229.0/24ARINValid
2604:13e0::/32ARINValid

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.