bgpreport

Network · data from 2026-11-12

AS264178 Coonexao Telecom e Informatica EIRELI

Registry name: AS264178 - Coonexao Telecom e Informatica EIRELI, BR · PeeringDB

4IPv4 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
2Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS264178, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264178, 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.72.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67
138.99.74.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67
2804:23b4::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
138.99.74.0/24 Valid Other IRR onlyALTDB, RADB 35 5%low visibility 26
138.99.75.0/24 Valid Other IRR onlyALTDB, RADB 35 5%low visibility 26

AS-SET

PeeringDB's irr_as_set for AS264178: AS-264178. 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 (AS264178 isn't in the set, or no route object for AS264178 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 objectsAS264178 in itNot covered
AS-264178 ALTDB 2222 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 10 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR138.99.72.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR138.99.74.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:23b4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR138.99.74.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.35 of 673
Route object: RIR138.99.75.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.35 of 673

Route objects not announced

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

138.99.72.0/21RADBNo ROA
138.99.72.0/22ALTDB, RADB, TCValid
138.99.72.0/24ALTDB, RADBValid
138.99.73.0/24ALTDB, RADBValid
2804:3680::/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.