bgpreport

Network · data from 2026-11-12

AS53005 CONNECT TELECOMUNICACOES LTDA

Registry name: AS53005 - REDE CONNECT TELECOMUNICACOES LTDA, BR · PeeringDB

31IPv4 routes 100.0% RPKI valid · 64.5% with a route object
7IPv6 routes 100.0% RPKI valid · 42.9% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 15 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS53005, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53005, 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.

45.161.16.0/22 Valid None 668 99% 66
45.161.16.0/24 Valid None 668 99% 66
45.161.17.0/24 Valid None 668 99% 66
45.161.18.0/24 Valid None 668 99% 66
45.161.19.0/24 Valid None 668 99% 66
168.90.167.0/24 Valid None 668 99% 66
177.84.16.0/22 Valid None 668 99% 66
168.90.164.0/22 Valid None 667 99% 66
189.50.60.0/22 Valid None 667 99% 66
189.50.62.0/23 Valid None 667 99% 66
177.84.16.0/24 Valid None 665 99% 66
2804:548:1800::/39 Valid Nonecovered by 2804:548::/35 632 99% 67
2804:548:1a00::/47 Valid Nonecovered by 2804:548::/35 632 99% 67
2804:548:2000::/35 Valid Nonecovered by 2804:548::/32 632 99% 67
2804:548:6000::/35 Valid Nonecovered by 2804:548::/32 632 99% 67
45.188.120.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
177.66.240.0/21 Valid Other IRR onlyRADB, TC 671 100% 66
177.66.240.0/22 Valid Other IRR onlyTC 671 100% 66
170.238.164.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
170.238.167.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
45.188.122.0/24 Valid Other IRR onlyTC 669 99% 67
45.188.123.0/24 Valid Other IRR onlyTC 669 99% 67
177.66.244.0/22 Valid Other IRR onlyRADB, TC 668 99% 66
2804:548::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:548:c000::/35 Valid Other IRR onlyRADB 635 100% 67
2804:548::/35 Valid Other IRR onlyRADB 634 100% 69
177.66.240.0/23 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
177.66.240.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.241.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.242.0/23 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
177.66.242.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.243.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.244.0/23 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
177.66.244.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.245.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.246.0/23 Valid Other IRR onlyRADB, TC 1 0%low visibility 1
177.66.246.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
177.66.247.0/24 Valid Other IRR onlyTC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS53005: AS53005:AS-REDECONNECTTELECOM. 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 (AS53005 isn't in the set, or no route object for AS53005 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 objectsAS53005 in itNot covered
AS53005:AS-REDECONNECTTELECOM TC 133127 Yes 11

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

  • Route object: none15
  • Route object: RIR23
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none45.161.16.0/22No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none45.161.16.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none45.161.17.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none45.161.18.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none45.161.19.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none168.90.167.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none177.84.16.0/22No route object for it. Add a route object with origin AS53005 in the RIR database for the space.668 of 673
Route object: none168.90.164.0/22No route object for it. Add a route object with origin AS53005 in the RIR database for the space.667 of 673
Route object: none189.50.60.0/22No route object for it. Add a route object with origin AS53005 in the RIR database for the space.667 of 673
Route object: none189.50.62.0/23No route object for it. Add a route object with origin AS53005 in the RIR database for the space.667 of 673
Route object: none177.84.16.0/24No route object for it. Add a route object with origin AS53005 in the RIR database for the space.665 of 673
Route object: none2804:548:1800::/39No route object for it. A route object for 2804:548::/35 with origin AS53005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53005 in the RIR database for the space.632 of 636
Route object: none2804:548:1a00::/47No route object for it. A route object for 2804:548::/35 with origin AS53005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53005 in the RIR database for the space.632 of 636
Route object: none2804:548:2000::/35No route object for it. A route object for 2804:548::/32 with origin AS53005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53005 in the RIR database for the space.632 of 636
Route object: none2804:548:6000::/35No route object for it. A route object for 2804:548::/32 with origin AS53005 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53005 in the RIR database for the space.632 of 636
Route object: RIR45.188.120.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.66.240.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.66.240.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.238.164.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR170.238.167.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.188.122.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.188.123.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.66.244.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:548::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:548:c000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:548::/35Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR177.66.240.0/23Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.240.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.241.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.242.0/23Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.242.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.243.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.244.0/23Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.244.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.245.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.246.0/23Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.246.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR177.66.247.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

45.188.120.0/23TCValid
45.188.120.0/24TCValid
45.188.121.0/24TCValid
45.188.122.0/23RADB, TCValid
170.238.164.0/23TCValid
170.238.164.0/24RADB, TCValid
170.238.165.0/24RADB, TCValid
170.238.166.0/23TCValid
170.238.166.0/24TCValid
2804:548:100::/40TCValid

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.