bgpreport

Network · data from 2026-11-12

AS264212 IMPACTO TELECOM

Registry name: AS264212 - IMPACTO TELECOMUNICACOES EIRELI - ME, BR · PeeringDB

29IPv4 routes 100.0% RPKI valid · 100.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 0 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS264212, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264212, 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.99.160.0/22 Valid Other IRR onlyRADB 672 100% 66
187.0.228.0/22 Valid Other IRR onlyRADB 672 100% 66
187.0.232.0/22 Valid Other IRR onlyRADB 672 100% 66
187.0.239.0/24 Valid Other IRR onlyRADB 672 100% 66
138.99.160.0/24 Valid Other IRR onlyRADB 671 100% 67
138.99.163.0/24 Valid Other IRR onlyRADB 671 100% 66
187.0.224.0/22 Valid Other IRR onlyRADB 671 100% 66
187.0.238.0/24 Valid Other IRR onlyRADB 671 100% 66
138.99.162.0/24 Valid Other IRR onlyRADB 666 99% 67
2804:2448::/32 Valid Other IRR onlyRADB 630 99% 67
187.0.234.0/24 Valid Other IRR onlyRADB 205 30% 55
138.99.160.0/23 Valid Other IRR onlyRADB 201 30% 54
138.99.162.0/23 Valid Other IRR onlyRADB 201 30% 54
187.0.232.0/23 Valid Other IRR onlyRADB 201 30% 54
187.0.234.0/23 Valid Other IRR onlyRADB 201 30% 54
187.0.226.0/23 Valid Other IRR onlyRADB 200 30% 54
187.0.228.0/23 Valid Other IRR onlyRADB 200 30% 54
187.0.230.0/23 Valid Other IRR onlyRADB 200 30% 54
138.99.161.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.224.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.225.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.226.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.227.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.228.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.229.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.230.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.231.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.232.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.233.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24
187.0.235.0/24 Valid Other IRR onlyRADB 58 9%low visibility 24

AS-SET

PeeringDB's irr_as_set for AS264212: AS264212:AS-CONE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS264212 isn't in the set, or no route object for AS264212 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS264212 in itNot covered
AS264212:AS-CONE RADB 2281 Yes 0

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

  • Route object: RIR30
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: RIR138.99.160.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.228.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.232.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.0.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.99.160.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.99.163.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.0.224.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.0.238.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.99.162.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:2448::/32Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR187.0.234.0/24Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR138.99.160.0/23Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR138.99.162.0/23Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR187.0.232.0/23Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR187.0.234.0/23Route object only in RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR187.0.226.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR187.0.228.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR187.0.230.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR138.99.161.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.224.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.225.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.226.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.227.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.228.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.229.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.230.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.231.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.232.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.233.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673
Route object: RIR187.0.235.0/24Route object only in RADB. Add it in the RIR database for the space.58 of 673

Route objects not announced

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

187.0.224.0/21RADBValid
187.0.224.0/23RADBValid
187.0.238.0/23RADBValid
2804:2448::/33RADBValid
2804:2448::/34RADBValid
2804:2448:4000::/34RADBValid
2804:2448:8000::/33RADBValid
2804:2448:8000::/34RADBValid
2804:2448:c000::/34RADBValid

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.