bgpreport

Network · data from 2026-11-12

AS273301 SIZATEK SPECTRUM

Registry name: AS273301 - SIZATEK SPECTRUM, MX · PeeringDB

2IPv4 routes 50.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
2No ROA 0 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS273301, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273301, 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.
38.190.96.0/23 No ROA Other IRR onlyRADB 670 100% 67
2001:1269::/32 No ROA Other IRR onlyRADB 633 100% 69
89.42.113.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

AS273301'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 4 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none38.190.96.0/23No ROA covers it. Add a ROA for AS273301, maxLength 23.670 of 673
Route object: RIR38.190.96.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2001:1269::/32No ROA covers it. Add a ROA for AS273301, maxLength 32.633 of 636
Route object: RIR2001:1269::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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