bgpreport

Network · data from 2026-11-12

AS272054 MUNDO1TELECOM

Registry name: AS272054 - MUNDO1TELECOM, S.R.L., DO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272054, 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.
204.137.174.0/24 Invalid: origin None 13 2%low visibility 9
206.0.18.0/24 Invalid: origin None 13 2%low visibility 9
206.0.19.0/24 Invalid: origin None 13 2%low visibility 9
2803:dd10:fe00::/40 No ROA Other IRR onlyRADB 633 100% 69
2803:dd10:ff00::/40 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS272054'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 11 are in fix.csv.

  • ROA: origin3
  • ROA: none2
  • Route object: none3
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin204.137.174.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS272054 should announce it, add a ROA for AS272054.13 of 673
Route object: none204.137.174.0/24No route object for it. Add a route object with origin AS272054 in the RIR database for the space.13 of 673
ROA: origin206.0.18.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS272054 should announce it, add a ROA for AS272054.13 of 673
Route object: none206.0.18.0/24No route object for it. Add a route object with origin AS272054 in the RIR database for the space.13 of 673
ROA: origin206.0.19.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS272054 should announce it, add a ROA for AS272054.13 of 673
Route object: none206.0.19.0/24No route object for it. Add a route object with origin AS272054 in the RIR database for the space.13 of 673
ROA: none2803:dd10:fe00::/40No ROA covers it. Add a ROA for AS272054, maxLength 40.633 of 636
Route object: RIR2803:dd10:fe00::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2803:dd10:ff00::/40No ROA covers it. Add a ROA for AS272054, maxLength 40.633 of 636
Route object: RIR2803:dd10:ff00::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

2803:dd10::/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.