bgpreport

Network · data from 2026-11-12

AS11622 InfoSpace, Inc.

Registry name: OFPD - Orland Fire Protection District, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS11622, 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.
104.238.238.0/24 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS11622'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 13 are in fix.csv.

  • ROA: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none104.238.238.0/24No ROA covers it. Add a ROA for AS11622, maxLength 24.672 of 673

Route objects not announced

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

66.150.4.0/24RADBNo ROA
72.53.192.0/21RADBNo ROA
72.53.199.0/24RADBNo ROA
72.53.200.0/22RADBNo ROA
72.53.204.0/23RADBNo ROA
72.53.204.0/24RADBNo ROA
72.53.205.0/24RADBNo ROA
72.53.253.0/24RADBNo ROA
72.53.254.0/23RADBNo ROA
206.29.192.0/22RADBNo ROA
206.29.196.0/23RADBNo ROA
206.29.198.0/26RADBNo 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.