bgpreport

Network · data from 2026-11-12

AS7011 FRONTIER-AND-CITIZENS - Frontier Communications of America, Inc.

Registry name: FRONTIER-AND-CITIZENS - Frontier Communications of America, Inc., US · not in PeeringDB

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

Announced routes

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

173.84.233.0/24 Valid RIR databaseARIN, RADB 667 99% 67
74.39.134.0/24 Valid RIR databaseARIN, RADB 666 99% 67
74.40.44.0/24 Valid RIR databaseARIN, RADB 666 99% 67
74.44.1.0/24 Valid RIR databaseARIN, RADB 666 99% 67

AS-SET

AS7011 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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

66.243.221.0/24RADBNo ROA
71.181.60.0/23RADBNo ROA
76.76.253.0/24RADBNo ROA
141.123.51.0/24RADBNo ROA
141.123.201.0/24RADBNo ROA
141.123.202.0/24RADBNo ROA
162.242.68.0/23RADBNo ROA
192.107.247.0/24RADBNo ROA
192.112.60.0/24RADBNo ROA
198.180.252.0/24RADBNo ROA
199.73.87.0/24RADBNo ROA
199.190.48.0/21RADBNo ROA
199.248.251.0/24RADBNo ROA
209.54.92.0/23RADBNo ROA
216.227.36.0/24RADBNo 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.