bgpreport

Network · data from 2026-11-12

AS270844 AXION3 TELECOM

Registry name: AS270844 - AXION3 TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270844, 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.
2804:91c8:4000::/36 No ROA None 46 7%low visibility 29
190.115.211.0/24 No ROA Other IRR onlyRADB 672 100% 67
190.115.210.0/24 No ROA Other IRR onlyRADB 671 100% 67
190.115.208.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:7248::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
190.115.209.0/24 No ROA Other IRR onlyRADB 253 38% 57

AS-SET

AS270844'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 15 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:91c8:4000::/36No ROA covers it. Add a ROA for AS270844, maxLength 36.46 of 636
Route object: none2804:91c8:4000::/36No route object for it. Add a route object with origin AS270844 in the RIR database for the space.46 of 636
ROA: none190.115.211.0/24No ROA covers it. Add a ROA for AS270844, maxLength 24.672 of 673
Route object: RIR190.115.211.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none190.115.210.0/24No ROA covers it. Add a ROA for AS270844, maxLength 24.671 of 673
Route object: RIR190.115.210.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none190.115.208.0/24No ROA covers it. Add a ROA for AS270844, maxLength 24.667 of 673
Route object: RIR190.115.208.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:7248::/32No ROA covers it. Add a ROA for AS270844, maxLength 32.634 of 636
Route object: RIR2804:7248::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none190.115.209.0/24No ROA covers it. Add a ROA for AS270844, maxLength 24.253 of 673
Route object: RIR190.115.209.0/24Route object only in RADB. Add it in the RIR database for the space.253 of 673

Route objects not announced

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

190.115.208.0/22RADB, TCNo ROA
2804:7248::/33RADBNo ROA
2804:7248:8000::/33RADBNo 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.