bgpreport

Network · data from 2026-11-12

AS32703 Intelligent Fiber Network

Registry name: IFN-NET - Zayo Bandwidth, US · PeeringDB

12IPv4 routes 83.3% RPKI valid · 0.0% with a route object
5IPv6 routes 80.0% RPKI valid · 40.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No ROA 15 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS32703, seen from no peer

Announced routes

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

23.247.180.0/24 No ROA None 673 100% 67
208.67.112.0/24 No ROA Other origin only 673 100% 67
2620:4a:c000::/48 No ROA None 635 100% 68
64.184.1.0/24 Valid None 673 100% 67
64.184.2.0/23 Valid None 673 100% 67
64.184.105.0/24 Valid None 673 100% 67
69.160.192.0/19 Valid None 673 100% 67
143.55.192.0/19 Valid None 673 100% 67
208.103.0.0/18 Valid None 673 100% 67
208.103.7.0/24 Valid None 673 100% 67
208.103.11.0/24 Valid None 673 100% 67
208.103.51.0/24 Valid None 672 100% 67
64.184.0.0/17 Valid None 670 100% 67
2600:100:102::/48 Valid None 635 100% 68
2600:100::/28 Valid None 634 100% 68
2607:fb08:8000::/48 Valid RIR databaseARIN 635 100% 68
2607:fb08::/32 Valid RIR databaseARIN 632 99% 68

AS-SET

PeeringDB's irr_as_set for AS32703: AS-IFN-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS32703 isn't in the set, or no route object for AS32703 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS32703 in itNot covered
AS-IFN-TRANSIT In no IRR database read today.

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

  • ROA: none3
  • Route object: none15
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none23.247.180.0/24No ROA covers it. Add a ROA for AS32703, maxLength 24.673 of 673
Route object: none23.247.180.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
ROA: none208.67.112.0/24No ROA covers it. Add a ROA for AS32703, maxLength 24.673 of 673
Route object: none208.67.112.0/24Route objects for it name AS53989. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
ROA: none2620:4a:c000::/48No ROA covers it. Add a ROA for AS32703, maxLength 48.635 of 636
Route object: none2620:4a:c000::/48No route object for it. Add a route object with origin AS32703 in the RIR database for the space.635 of 636
Route object: none64.184.1.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none64.184.2.0/23No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none64.184.105.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none69.160.192.0/19No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none143.55.192.0/19No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none208.103.0.0/18No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none208.103.7.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none208.103.11.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.673 of 673
Route object: none208.103.51.0/24No route object for it. Add a route object with origin AS32703 in the RIR database for the space.672 of 673
Route object: none64.184.0.0/17No route object for it. Add a route object with origin AS32703 in the RIR database for the space.670 of 673
Route object: none2600:100:102::/48No route object for it. Add a route object with origin AS32703 in the RIR database for the space.635 of 636
Route object: none2600:100::/28No route object for it. Add a route object with origin AS32703 in the RIR database for the space.634 of 636
AS-SET: not foundAS-IFN-TRANSITPeeringDB names AS-IFN-TRANSIT; no IRR database read has it.

Route objects not announced

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

64.184.16.0/22ARINInvalid: maxLength
64.184.22.0/24ARINInvalid: maxLength

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.