bgpreport

Network · data from 2026-11-12

AS398734 FLEETTEL-AS01 - Fleettel INC

Registry name: FLEETTEL-AS01 - Fleettel INC, CA · not in PeeringDB

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

Announced routes

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

165.140.100.0/24 No ROA Nonecovered by 165.140.100.0/22 673 100% 67
165.140.101.0/24 No ROA Nonecovered by 165.140.100.0/22 673 100% 67
165.140.103.0/24 No ROA Nonecovered by 165.140.100.0/22 673 100% 67
23.150.144.0/24 No ROA Other origin only 671 100% 67
199.119.73.0/24 No ROA Other origin only 671 100% 67
199.119.74.0/24 No ROA Other origin only 671 100% 67
199.119.75.0/24 No ROA Other origin only 671 100% 67
2606:e940::/48 No ROA None 604 95% 67

AS-SET

AS398734 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none165.140.100.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.673 of 673
Route object: none165.140.100.0/24No route object for it. A route object for 165.140.100.0/22 with origin AS398734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398734 in the RIR database for the space.673 of 673
ROA: none165.140.101.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.673 of 673
Route object: none165.140.101.0/24No route object for it. A route object for 165.140.100.0/22 with origin AS398734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398734 in the RIR database for the space.673 of 673
ROA: none165.140.103.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.673 of 673
Route object: none165.140.103.0/24No route object for it. A route object for 165.140.100.0/22 with origin AS398734 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398734 in the RIR database for the space.673 of 673
ROA: none23.150.144.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.671 of 673
Route object: none23.150.144.0/24Route objects for it name AS7883. Add a route object with origin AS398734 in the RIR database for the space.671 of 673
ROA: none199.119.73.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.671 of 673
Route object: none199.119.73.0/24Route objects for it name AS7883. Add a route object with origin AS398734 in the RIR database for the space.671 of 673
ROA: none199.119.74.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.671 of 673
Route object: none199.119.74.0/24Route objects for it name AS7883. Add a route object with origin AS398734 in the RIR database for the space.671 of 673
ROA: none199.119.75.0/24No ROA covers it. Add a ROA for AS398734, maxLength 24.671 of 673
Route object: none199.119.75.0/24Route objects for it name AS7883. Add a route object with origin AS398734 in the RIR database for the space.671 of 673
ROA: none2606:e940::/48No ROA covers it. Add a ROA for AS398734, maxLength 48.604 of 636
Route object: none2606:e940::/48No route object for it. Add a route object with origin AS398734 in the RIR database for the space.604 of 636

Route objects not announced

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

38.80.70.0/24RADBNo ROA
165.140.100.0/22ARIN, 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.