bgpreport

Network · data from 2026-11-12

AS63003 Infra-Solutions

Registry name: INFRA-SOLUTIONS - Infra-Solutions inc., CA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63003, 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.
2607:1d00::/32 No ROA RIR databaseARIN 1 0%low visibility 1

AS-SET

AS63003'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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2607:1d00::/32No ROA covers it. Add a ROA for AS63003, maxLength 32.1 of 636

Route objects not announced

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

107.161.96.0/20ARINNo ROA
107.161.104.0/21ARINNo ROA

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.