bgpreport

Network · data from 2026-11-12

AS1088 FASTBRIDGE-FIBER-RDNG-PA-01 - FastBridge Fiber

Registry name: FASTBRIDGE-FIBER-RDNG-PA-01 - FastBridge Fiber, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1088, 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.
38.34.128.0/22 No ROA Nonecovered by 38.34.128.0/19 673 100% 67
38.34.132.0/22 No ROA Nonecovered by 38.34.128.0/19 673 100% 67
38.34.136.0/21 No ROA Other origin onlycovered by 38.34.128.0/19 673 100% 67
38.34.144.0/20 No ROA Nonecovered by 38.34.128.0/19 673 100% 67
38.102.12.0/23 No ROA RIR databaseARIN 673 100% 67
154.13.164.0/22 No ROA RIR databaseARIN 673 100% 67
147.185.187.0/24 Valid RIR databaseARIN, RADB 673 100% 67
167.94.99.0/24 Valid RIR databaseARIN, RADB 673 100% 67
2606:ea40::/32 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS1088 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 11 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.34.128.0/22No ROA covers it. Add a ROA for AS1088, maxLength 22.673 of 673
Route object: none38.34.128.0/22No route object for it. A route object for 38.34.128.0/19 with origin AS1088 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1088 in the RIR database for the space.673 of 673
ROA: none38.34.132.0/22No ROA covers it. Add a ROA for AS1088, maxLength 22.673 of 673
Route object: none38.34.132.0/22No route object for it. A route object for 38.34.128.0/19 with origin AS1088 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1088 in the RIR database for the space.673 of 673
ROA: none38.34.136.0/21No ROA covers it. Add a ROA for AS1088, maxLength 21.673 of 673
Route object: none38.34.136.0/21Route objects for it name AS7029. A route object for 38.34.128.0/19 with origin AS1088 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1088 in the RIR database for the space.673 of 673
ROA: none38.34.144.0/20No ROA covers it. Add a ROA for AS1088, maxLength 20.673 of 673
Route object: none38.34.144.0/20No route object for it. A route object for 38.34.128.0/19 with origin AS1088 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1088 in the RIR database for the space.673 of 673
ROA: none38.102.12.0/23No ROA covers it. Add a ROA for AS1088, maxLength 23.673 of 673
ROA: none154.13.164.0/22No ROA covers it. Add a ROA for AS1088, maxLength 22.673 of 673

Route objects not announced

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

38.34.128.0/19ARIN, RADBNo 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.