bgpreport

Network · data from 2026-11-12

AS2033 PANIX - Panix

Registry name: PANIX - Panix, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2033, 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.
206.54.128.0/20 No ROA Other IRR onlyPANIX 673 100% 67
204.52.227.0/24 No ROA Other IRR onlyPANIX 671 100% 68
204.52.248.0/23 No ROA Other IRR onlyPANIX 671 100% 68
206.223.36.0/24 No ROA Other IRR onlyPANIX 671 100% 68
166.84.160.0/22 Valid Nonecovered by 166.84.0.0/16 671 100% 68
198.7.4.0/22 Valid Nonecovered by 198.7.0.0/21 671 100% 68
166.84.0.0/16 Valid RIR databaseARIN, PANIX 671 100% 68
198.7.0.0/21 Valid RIR databaseARIN, PANIX 671 100% 68
198.186.151.0/24 Valid RIR databaseARIN, PANIX 671 100% 68
204.29.154.0/24 Valid RIR databaseARIN, PANIX 671 100% 68
2602:f977::/36 Valid RIR databaseARIN, PANIX 635 100% 69

AS-SET

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

  • ROA: none4
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none206.54.128.0/20No ROA covers it. Add a ROA for AS2033, maxLength 20.673 of 673
Route object: RIR206.54.128.0/20Route object only in PANIX. Add it in the RIR database for the space.673 of 673
ROA: none204.52.227.0/24No ROA covers it. Add a ROA for AS2033, maxLength 24.671 of 673
Route object: RIR204.52.227.0/24Route object only in PANIX. Add it in the RIR database for the space.671 of 673
ROA: none204.52.248.0/23No ROA covers it. Add a ROA for AS2033, maxLength 23.671 of 673
Route object: RIR204.52.248.0/23Route object only in PANIX. Add it in the RIR database for the space.671 of 673
ROA: none206.223.36.0/24No ROA covers it. Add a ROA for AS2033, maxLength 24.671 of 673
Route object: RIR206.223.36.0/24Route object only in PANIX. Add it in the RIR database for the space.671 of 673
Route object: none166.84.160.0/22No route object for it. A route object for 166.84.0.0/16 with origin AS2033 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2033 in the RIR database for the space.671 of 673
Route object: none198.7.4.0/22No route object for it. A route object for 198.7.0.0/21 with origin AS2033 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2033 in the RIR database for the space.671 of 673

Route objects not announced

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

2001:470:30::/48BBOIInvalid: origin
2001:470:38d::/48ARINValid

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.