bgpreport

Network · data from 2026-11-12

AS264022 REDE CONEXAONET

Registry name: AS264022 - REDE CONEXAONET, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264022, 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:2990:c000::/35 Valid Nonecovered by 2804:2990:c000::/34 344 54% 64
2804:2990:e000::/35 Valid Nonecovered by 2804:2990:c000::/34 344 54% 64
143.0.222.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
143.0.220.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
143.0.221.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
143.0.223.0/24 Valid Other IRR onlyTC 667 99% 67
143.0.220.0/23 Valid Other IRR onlyRADB, TC 666 99% 66
2804:2990::/33 Valid Other IRR onlyRADB, TC 631 99% 69
2804:2990:1500::/40 Valid Other IRR onlyRADB 631 99% 69
2804:2990:8000::/33 Valid Other IRR onlyRADB, TC 631 99% 69
2804:2990:8100::/40 Valid Other IRR onlyRADB 631 99% 69
2804:2990:d000::/36 Valid Other IRR onlyRADB 631 99% 69
2804:2990::/32 Valid Other IRR onlyRADB, TC 630 99% 69
2804:2990:8000::/40 Valid Other IRR onlyRADB 630 99% 69
2804:2990:c000::/34 Valid Other IRR onlyRADB, TC 630 99% 69

AS-SET

PeeringDB's irr_as_set for AS264022: AS264022:AS-ANNOUNCEMENTS. 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 (AS264022 isn't in the set, or no route object for AS264022 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 objectsAS264022 in itNot covered
AS264022:AS-ANNOUNCEMENTS TC 2244 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 19 are in fix.csv.

  • Route object: none2
  • Route object: RIR13
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2804:2990:c000::/35No route object for it. A route object for 2804:2990:c000::/34 with origin AS264022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264022 in the RIR database for the space.344 of 636
Route object: none2804:2990:e000::/35No route object for it. A route object for 2804:2990:c000::/34 with origin AS264022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264022 in the RIR database for the space.344 of 636
Route object: RIR143.0.222.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR143.0.220.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.0.221.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR143.0.223.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR143.0.220.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:2990::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2990:1500::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2990:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2990:8100::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2990:d000::/36Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:2990::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2990:8000::/40Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:2990:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

143.0.220.0/22RADB, TCNo ROA
143.0.222.0/23RADB, TCNo ROA
170.245.172.0/22RADBNo ROA
170.245.172.0/23ALTDB, RADBNo 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.