bgpreport

Network · data from 2026-11-12

AS52284 Panamaserver.com

Registry name: AS52284 - Panamaserver.com, PA · PeeringDB

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

Announced routes

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

142.202.136.0/24 No ROA Other IRR onlyRADB 671 100% 67
190.123.44.0/24 Valid Nonecovered by 190.123.44.0/22 667 99% 67
190.123.45.0/24 Valid Nonecovered by 190.123.44.0/22 667 99% 67
190.123.46.0/24 Valid Nonecovered by 190.123.44.0/22 667 99% 67
190.123.47.0/24 Valid Other IRR onlyRADB 667 99% 67
2803:200::/32 Valid RIR databaseLACNIC, RADB 634 100% 67

AS-SET

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

  • ROA: none1
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none142.202.136.0/24No ROA covers it. Add a ROA for AS52284, maxLength 24.671 of 673
Route object: RIR142.202.136.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none190.123.44.0/24No route object for it. A route object for 190.123.44.0/22 with origin AS52284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52284 in the RIR database for the space.667 of 673
Route object: none190.123.45.0/24No route object for it. A route object for 190.123.44.0/22 with origin AS52284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52284 in the RIR database for the space.667 of 673
Route object: none190.123.46.0/24No route object for it. A route object for 190.123.44.0/22 with origin AS52284 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52284 in the RIR database for the space.667 of 673
Route object: RIR190.123.47.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

181.191.0.0/16RADBNo ROA
190.93.32.0/22RADBNo ROA
190.123.44.0/22LACNICValid
201.190.128.0/17RADBNo ROA
201.190.220.0/23RADBNo ROA
2803:1c00::/32RADBNo ROA

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.