bgpreport

Network · data from 2026-11-12

AS401725 Open Infra Inc.

Registry name: OPENINFRA-TX - Open Infra Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401725, 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.

2604:ae0:200::/40 Invalid: origin Other origin only 2 0%low visibility 2
23.128.56.0/24 No ROA Other origin only 673 100% 67
40.27.18.0/24 Valid RIR databaseARIN, RADB 670 100% 68
64.62.192.0/24 Valid RIR databaseARIN 670 100% 68
184.105.14.0/23 Valid RIR databaseARIN 670 100% 68
2604:ae0:f000::/40 Valid RIR databaseARIN 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS401725: ARIN::AS-OITX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS401725 isn't in the set, or no route object for AS401725 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS401725 in itNot covered
ARIN::AS-OITX ARIN 316 No 6

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: origin1
  • ROA: none1
  • Route object: none2
  • AS-SET: own ASN1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2604:ae0:200::/40ROAs covering it name AS401081, not AS401725. If AS401725 should announce it, add a ROA for AS401725.2 of 636
Route object: none2604:ae0:200::/40Route objects for it name AS401081. Add a route object with origin AS401725 in the RIR database for the space.2 of 636
ROA: none23.128.56.0/24No ROA covers it. Add a ROA for AS401725, maxLength 24.673 of 673
Route object: none23.128.56.0/24Route objects for it name AS400228. Add a route object with origin AS401725 in the RIR database for the space.673 of 673
AS-SET: own ASNARIN::AS-OITXAS401725 isn't in AS-OITX (ARIN) once expanded. Add AS401725 to it.

Route objects not announced

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

2001:470:2f1::/48ARINValid
2001:470:3a5::/48ARINValid
2604:ae0:140::/42ARINValid

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.