bgpreport

Network · data from 2026-11-12

AS27541 Frontier TeleNet

Registry name: FTNET - Frontier Telenet, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS27541, 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.
69.88.232.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.234.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.236.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.238.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.246.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.249.0/24 No ROA Other IRR onlyRADB 671 100% 68
69.88.250.0/23 No ROA Other IRR onlyRADB 671 100% 68
69.88.252.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.255.88.0/21 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

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

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none69.88.232.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.232.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.234.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.234.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.236.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.236.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.238.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.238.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.246.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.246.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.249.0/24No ROA covers it. Add a ROA for AS27541, maxLength 24.671 of 673
Route object: RIR69.88.249.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.250.0/23No ROA covers it. Add a ROA for AS27541, maxLength 23.671 of 673
Route object: RIR69.88.250.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none69.88.252.0/24No ROA covers it. Add a ROA for AS27541, maxLength 24.671 of 673
Route object: RIR69.88.252.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.255.88.0/21No ROA covers it. Add a ROA for AS27541, maxLength 21.671 of 673
Route object: RIR199.255.88.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS27541 is announced.

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.