bgpreport

Network · data from 2026-11-12

AS271861 AS271861 - MOVILMAX TELECOM S.A.

Registry name: AS271861 - MOVILMAX TELECOM S.A., PE · not in PeeringDB

5IPv4 routes 80.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
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS271861, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271861, 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.157.233.0/24 No ROA Other origin only 661 98% 66
131.255.136.0/24 Valid RIR databaseLACNIC 672 100% 67
131.255.137.0/24 Valid RIR databaseLACNIC 672 100% 67
131.255.138.0/24 Valid RIR databaseLACNIC 672 100% 67
131.255.139.0/24 Valid RIR databaseLACNIC 672 100% 67
2803:4780::/32 Valid RIR databaseLACNIC 635 100% 67

AS-SET

AS271861 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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none204.157.233.0/24No ROA covers it. Add a ROA for AS271861, maxLength 24.661 of 673
Route object: none204.157.233.0/24Route objects for it name AS269898. Add a route object with origin AS271861 in the RIR database for the space.661 of 673

Route objects not announced

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

131.255.136.0/22ALTDB, LACNICValid

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.