bgpreport

Network · data from 2026-11-12

AS263887 AS263887 - MANIA TELECOM

Registry name: AS263887 - MANIA TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263887, 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.
138.204.128.0/24 No ROA Other IRR onlyRADB 668 99% 66
138.204.131.0/24 No ROA Other IRR onlyRADB 667 99% 67
138.204.129.0/24 No ROA Other IRR onlyRADB 666 99% 67
138.204.130.0/24 No ROA Other IRR onlyRADB 665 99% 67
2804:2740:8000::/33 No ROA Other IRR onlyRADB 632 99% 67
2804:2740:4000::/40 No ROA Other IRR onlyRADB 631 99% 67
2804:2740:4100::/40 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

AS263887 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 17 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none138.204.128.0/24No ROA covers it. Add a ROA for AS263887, maxLength 24.668 of 673
Route object: RIR138.204.128.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none138.204.131.0/24No ROA covers it. Add a ROA for AS263887, maxLength 24.667 of 673
Route object: RIR138.204.131.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none138.204.129.0/24No ROA covers it. Add a ROA for AS263887, maxLength 24.666 of 673
Route object: RIR138.204.129.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none138.204.130.0/24No ROA covers it. Add a ROA for AS263887, maxLength 24.665 of 673
Route object: RIR138.204.130.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:2740:8000::/33No ROA covers it. Add a ROA for AS263887, maxLength 33.632 of 636
Route object: RIR2804:2740:8000::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none2804:2740:4000::/40No ROA covers it. Add a ROA for AS263887, maxLength 40.631 of 636
Route object: RIR2804:2740:4000::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:2740:4100::/40No ROA covers it. Add a ROA for AS263887, maxLength 40.631 of 636
Route object: RIR2804:2740:4100::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

138.204.128.0/22RADBNo ROA
138.204.130.0/23RADBNo ROA
2804:2740::/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.