bgpreport

Network · data from 2026-11-12

AS7883 ELPC-INC

Registry name: FLEETTEL-AS02 - Fleettel INC., CA · PeeringDB

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

Announced routes

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

130.51.72.0/24 No ROA None 673 100% 67
130.51.73.0/24 No ROA None 673 100% 67
130.51.74.0/24 No ROA None 673 100% 67
130.51.75.0/24 No ROA None 673 100% 67
165.140.102.0/24 No ROA None 673 100% 67
199.119.72.0/24 No ROA RIR databaseARIN, RADB 673 100% 67

AS-SET

AS7883'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 19 are in fix.csv.

  • ROA: none6
  • Route object: none5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none130.51.72.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673
Route object: none130.51.72.0/24No route object for it. Add a route object with origin AS7883 in the RIR database for the space.673 of 673
ROA: none130.51.73.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673
Route object: none130.51.73.0/24No route object for it. Add a route object with origin AS7883 in the RIR database for the space.673 of 673
ROA: none130.51.74.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673
Route object: none130.51.74.0/24No route object for it. Add a route object with origin AS7883 in the RIR database for the space.673 of 673
ROA: none130.51.75.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673
Route object: none130.51.75.0/24No route object for it. Add a route object with origin AS7883 in the RIR database for the space.673 of 673
ROA: none165.140.102.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673
Route object: none165.140.102.0/24No route object for it. Add a route object with origin AS7883 in the RIR database for the space.673 of 673
ROA: none199.119.72.0/24No ROA covers it. Add a ROA for AS7883, maxLength 24.673 of 673

Route objects not announced

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

23.150.144.0/24ARIN, RADBNo ROA
23.158.240.0/24RADBNo ROA
65.99.0.0/17RADBNo ROA
199.119.73.0/24ARIN, RADBNo ROA
199.119.74.0/24ARIN, RADBNo ROA
199.119.75.0/24ARIN, RADBNo ROA
2602:fd4e::/36RADBNo ROA
2602:fd78::/36ARIN, 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.