bgpreport

Network · data from 2026-11-12

AS53449 OEC Fiber

Registry name: OEC-FIBER - OEC Fiber, US · PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No 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 AS53449, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53449, 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.
164.90.32.0/19 No ROA RIR databaseARIN, RADB 673 100% 67
166.113.64.0/18 No ROA RIR databaseARIN, RADB 673 100% 67
170.89.64.0/18 No ROA RIR databaseARIN 673 100% 67
136.228.96.0/19 No ROA RIR databaseARIN, RADB 670 100% 67
158.62.128.0/18 No ROA RIR databaseARIN, RADB 670 100% 67
2604:a240::/32 No ROA RIR databaseARIN, RADB 630 99% 68

AS-SET

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

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none164.90.32.0/19No ROA covers it. Add a ROA for AS53449, maxLength 19.673 of 673
ROA: none166.113.64.0/18No ROA covers it. Add a ROA for AS53449, maxLength 18.673 of 673
ROA: none170.89.64.0/18No ROA covers it. Add a ROA for AS53449, maxLength 18.673 of 673
ROA: none136.228.96.0/19No ROA covers it. Add a ROA for AS53449, maxLength 19.670 of 673
ROA: none158.62.128.0/18No ROA covers it. Add a ROA for AS53449, maxLength 18.670 of 673
ROA: none2604:a240::/32No ROA covers it. Add a ROA for AS53449, maxLength 32.630 of 636

Route objects not announced

Every route object with origin AS53449 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.