bgpreport

Network · data from 2026-11-12

AS200154 IZONE LLC

Registry name: IZONE-AS IZONE LLC, AZ · PeeringDB

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

Announced routes

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

95.86.158.0/24 Invalid: origin Other origin only 1 0%low visibility 1
95.86.162.0/24 Invalid: origin Other origin only 0 0%low visibility 1
95.86.136.0/24 Valid RIR databaseRIPE 673 100% 66
185.32.45.0/24 Valid RIR databaseRIPE 673 100% 66
185.32.46.0/24 Valid RIR databaseRIPE 673 100% 66
185.32.47.0/24 Valid RIR databaseRIPE 673 100% 66
185.40.32.0/24 Valid RIR databaseRIPE 673 100% 66
185.40.33.0/24 Valid RIR databaseRIPE 673 100% 66
37.32.79.0/24 Valid RIR databaseRIPE 672 100% 66
46.32.163.0/24 Valid RIR databaseRIPE 672 100% 66
95.86.161.0/24 Valid RIR databaseRIPE 672 100% 66
185.32.44.0/24 Valid RIR databaseRIPE 672 100% 66
37.32.77.0/24 Valid RIR databaseRIPE 671 100% 66
46.32.176.0/24 Valid RIR databaseRIPE 671 100% 66
2a00:c0a0::/34 Valid RIR databaseRIPE 635 100% 67
2a00:c0a0:4000::/34 Valid RIR databaseRIPE 635 100% 67
2a00:c0a0:c000::/34 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS200154'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 8 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin95.86.158.0/24ROAs covering it name AS216231, not AS200154. If AS200154 should announce it, add a ROA for AS200154.1 of 673
Route object: none95.86.158.0/24Route objects for it name AS216231. Add a route object with origin AS200154 in the RIR database for the space.1 of 673
ROA: origin95.86.162.0/24ROAs covering it name AS218452, not AS200154. If AS200154 should announce it, add a ROA for AS200154.0 of 673
Route object: none95.86.162.0/24Route objects for it name AS218452. Add a route object with origin AS200154 in the RIR database for the space.0 of 673

Route objects not announced

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

45.194.84.0/24AFRINICInvalid: origin
154.47.6.0/24RADBNo ROA
185.32.44.0/22RIPEValid
2a00:c0a0::/32RIPEValid

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.