bgpreport

Network · data from 2026-11-12

AS40785 Omniva

Registry name: AS-OMNIVA-NJDC - Omniva LLC, US · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
4Route objects not announced registered with origin AS40785, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40785, 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.
23.163.72.0/24 Valid RIR databaseARIN, RADB 673 100% 67
163.165.189.0/24 Valid RIR databaseARIN 673 100% 67
2607:7040::/48 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS40785'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 4 are in fix.csv.

  • Route object: not announced4

Route objects not announced

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

38.111.116.0/24RADBNo ROA
63.145.143.0/24RADBNo ROA
2607:7040::/47ARINValid
2607:7040:1::/48ARINValid

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.