bgpreport

Network · data from 2026-11-12

AS35910 LOVES-TRAVEL-STOPS - Love's Travel Stops & Country Stores Inc.

Registry name: LOVES-TRAVEL-STOPS - Love's Travel Stops & Country Stores Inc., US · not in PeeringDB

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

Announced routes

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

12.71.189.0/24 No ROA None 673 100% 67
204.115.14.0/23 No ROA RIR databaseARIN 671 100% 67
24.248.247.0/24 Valid Other origin only 41 6%low visibility 29

AS-SET

AS35910 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 6 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none12.71.189.0/24No ROA covers it. Add a ROA for AS35910, maxLength 24.673 of 673
Route object: none12.71.189.0/24No route object for it. Add a route object with origin AS35910 in the RIR database for the space.673 of 673
ROA: none204.115.14.0/23No ROA covers it. Add a ROA for AS35910, maxLength 23.671 of 673
Route object: none24.248.247.0/24Route objects for it name AS19905. Add a route object with origin AS35910 in the RIR database for the space.41 of 673

Route objects not announced

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

204.115.14.0/24ARINNo ROA
204.115.15.0/24ARINNo 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.