bgpreport

Network · data from 2026-11-12

AS264013 CONNECTA TELECOM INTERNET

Registry name: AS264013 - CONNECTA TELECOM INTERNET LTDA - EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264013, 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:2968:100::/40 Valid Nonecovered by 2804:2968::/33 633 100% 67
2804:2968:80::/41 Valid Nonecovered by 2804:2968::/33 631 99% 67
2804:2968:6000::/41 Valid Nonecovered by 2804:2968::/33 631 99% 67
2804:2968:8001::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
2804:2968:8002::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
2804:2968:8003::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
2804:2968:8004::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
2804:2968:8005::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
2804:2968:8006::/48 Valid Nonecovered by 2804:2968::/32 631 99% 67
187.120.189.0/24 Valid Nonecovered by 187.120.188.0/23 198 29% 54
143.0.184.0/22 Valid Other IRR onlyALTDB, RADB 672 100% 66
187.120.176.0/20 Valid Other IRR onlyALTDB 672 100% 66
187.120.176.0/21 Valid Other IRR onlyALTDB 672 100% 66
143.0.184.0/23 Valid Other IRR onlyALTDB 671 100% 66
143.0.186.0/23 Valid Other IRR onlyALTDB 671 100% 66
170.0.152.0/23 Valid Other IRR onlyALTDB 671 100% 66
170.0.154.0/23 Valid Other IRR onlyALTDB 671 100% 66
187.120.184.0/21 Valid Other IRR onlyALTDB 671 100% 66
187.120.186.0/24 Valid Other IRR onlyALTDB 671 100% 67
187.120.184.0/24 Valid Other IRR onlyALTDB 670 100% 67
2804:2968::/32 Valid Other IRR onlyALTDB, RADB 630 99% 67
143.0.184.0/24 Valid Other IRR onlyALTDB 198 29% 54
143.0.187.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.176.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.177.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.178.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.179.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.180.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.181.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.182.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.183.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.185.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.187.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.188.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.190.0/24 Valid Other IRR onlyALTDB 198 29% 54
187.120.191.0/24 Valid Other IRR onlyALTDB 198 29% 54
143.0.185.0/24 Valid Other IRR onlyALTDB 197 29% 54
143.0.186.0/24 Valid Other IRR onlyALTDB 197 29% 54
170.0.154.0/24 Valid Other IRR onlyALTDB 197 29% 54
170.0.155.0/24 Valid Other IRR onlyALTDB 197 29% 54

AS-SET

PeeringDB's irr_as_set for AS264013: AS-264013:AS264013. 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 (AS264013 isn't in the set, or no route object for AS264013 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 objectsAS264013 in itNot covered
AS-264013:AS264013 In no IRR database read today.

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

  • Route object: none10
  • Route object: RIR30
  • AS-SET: not found1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
Route object: none2804:2968:100::/40No route object for it. A route object for 2804:2968::/33 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.633 of 636
Route object: none2804:2968:80::/41No route object for it. A route object for 2804:2968::/33 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:6000::/41No route object for it. A route object for 2804:2968::/33 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8001::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8002::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8003::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8004::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8005::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none2804:2968:8006::/48No route object for it. A route object for 2804:2968::/32 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.631 of 636
Route object: none187.120.189.0/24No route object for it. A route object for 187.120.188.0/23 with origin AS264013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264013 in the RIR database for the space.198 of 673
Route object: RIR143.0.184.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.176.0/20Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.176.0/21Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.184.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR143.0.186.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.0.152.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.0.154.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.184.0/21Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.186.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.184.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:2968::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR143.0.184.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR143.0.187.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.176.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.177.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.178.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.179.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.180.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.181.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.182.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.183.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.185.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.187.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.188.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.190.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR187.120.191.0/24Route object only in ALTDB. Add it in the RIR database for the space.198 of 673
Route object: RIR143.0.185.0/24Route object only in ALTDB. Add it in the RIR database for the space.197 of 673
Route object: RIR143.0.186.0/24Route object only in ALTDB. Add it in the RIR database for the space.197 of 673
Route object: RIR170.0.154.0/24Route object only in ALTDB. Add it in the RIR database for the space.197 of 673
Route object: RIR170.0.155.0/24Route object only in ALTDB. Add it in the RIR database for the space.197 of 673
AS-SET: not foundAS-264013:AS264013PeeringDB names AS-264013:AS264013; no IRR database read has it.

Route objects not announced

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

170.0.152.0/22RADBNo ROA
170.0.152.0/24ALTDBValid
170.0.153.0/24ALTDBValid
187.120.176.0/22ALTDBValid
187.120.176.0/23ALTDBValid
187.120.178.0/23ALTDBValid
187.120.180.0/22ALTDBValid
187.120.180.0/23ALTDBValid
187.120.182.0/23ALTDBValid
187.120.184.0/22ALTDBValid
187.120.184.0/23ALTDBValid
187.120.186.0/23ALTDBValid
187.120.188.0/22ALTDBValid
187.120.188.0/23ALTDBValid
187.120.190.0/23ALTDBValid
2804:2968::/33ALTDBValid

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.