bgpreport

Network · data from 2026-11-12

AS270078 TOPMANAGE DE PANAMA

Registry name: AS270078 - TOPMANAGE DE PANAMA S.A., PA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270078, 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.
200.71.80.0/24 Valid Nonecovered by 200.71.80.0/23 665 99% 67
200.71.81.0/24 Valid Nonecovered by 200.71.80.0/23 665 99% 67
2803:4be0:2::/48 Valid Nonecovered by 2803:4be0::/32 631 99% 67
2803:4be0:2a::/48 Valid Nonecovered by 2803:4be0::/32 631 99% 67
2803:4be0:1::/48 Valid Nonecovered by 2803:4be0::/32 2 0%low visibility 1
2803:4be0:1a::/48 Valid Nonecovered by 2803:4be0::/32 2 0%low visibility 1
200.71.80.0/23 Valid RIR databaseLACNIC 667 99% 67
2803:4be0::/32 Valid RIR databaseLACNIC, RADB 631 99% 67

AS-SET

AS270078'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.

  • Route object: none6
ChangePrefix or setDetailFull-table peers
Route object: none200.71.80.0/24No route object for it. A route object for 200.71.80.0/23 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.665 of 673
Route object: none200.71.81.0/24No route object for it. A route object for 200.71.80.0/23 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.665 of 673
Route object: none2803:4be0:2::/48No route object for it. A route object for 2803:4be0::/32 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.631 of 636
Route object: none2803:4be0:2a::/48No route object for it. A route object for 2803:4be0::/32 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.631 of 636
Route object: none2803:4be0:1::/48No route object for it. A route object for 2803:4be0::/32 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.2 of 636
Route object: none2803:4be0:1a::/48No route object for it. A route object for 2803:4be0::/32 with origin AS270078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270078 in the RIR database for the space.2 of 636

Route objects not announced

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