bgpreport

Network · data from 2026-11-12

AS264631 RED PARAGUAYA DE TELECOMUNICACIONES SA

Registry name: AS264631 - RED PARAGUAYA DE TELECOMUNICACIONES SA, PY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264631, 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.
45.235.120.0/22 Valid None 669 99% 67
143.202.208.0/24 Valid Nonecovered by 143.202.208.0/23 201 30% 56
143.202.208.0/22 Valid Other IRR onlyRADB 672 100% 66
143.202.208.0/23 Valid Other IRR onlyRADB 672 100% 66
143.202.210.0/23 Valid Other IRR onlyRADB 672 100% 66
2803:e140::/32 Valid Other IRR onlyRADB 634 100% 67
143.202.209.0/24 Valid Other IRR onlyRADB 201 30% 56
143.202.210.0/24 Valid Other IRR onlyRADB 201 30% 56
143.202.211.0/24 Valid Other IRR onlyRADB 201 30% 56

AS-SET

AS264631'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 9 are in fix.csv.

  • Route object: none2
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none45.235.120.0/22No route object for it. Add a route object with origin AS264631 in the RIR database for the space.669 of 673
Route object: none143.202.208.0/24No route object for it. A route object for 143.202.208.0/23 with origin AS264631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264631 in the RIR database for the space.201 of 673
Route object: RIR143.202.208.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.202.208.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.202.210.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2803:e140::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR143.202.209.0/24Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR143.202.210.0/24Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR143.202.211.0/24Route object only in RADB. Add it in the RIR database for the space.201 of 673

Route objects not announced

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