bgpreport

Network · data from 2026-11-12

AS53138 Conectlan

Registry name: AS53138 - Conectlan Internet Ltda, BR · PeeringDB

37IPv4 routes 100.0% RPKI valid · 94.6% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 4 with no route object for this origin
21Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS53138, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS53138, 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:140::/33 Valid Nonecovered by 2804:140::/32 631 99% 67
2804:140:8000::/33 Valid Nonecovered by 2804:140::/32 630 99% 67
186.192.249.0/24 Valid Nonecovered by 186.192.248.0/23 2 0%low visibility 2
186.192.252.0/24 Valid Nonecovered by 186.192.252.0/23 2 0%low visibility 2
177.53.224.0/21 Valid Other IRR onlyRADB, TC 668 99% 67
177.53.231.0/24 Valid Other IRR onlyRADB 668 99% 67
186.192.240.0/20 Valid Other IRR onlyRADB, TC 668 99% 67
186.192.254.0/24 Valid Other IRR onlyRADB 668 99% 67
177.53.224.0/22 Valid Other IRR onlyRADB 667 99% 67
177.53.224.0/23 Valid Other IRR onlyRADB 667 99% 67
177.53.226.0/23 Valid Other IRR onlyRADB 667 99% 67
177.53.228.0/22 Valid Other IRR onlyRADB 667 99% 67
177.53.228.0/23 Valid Other IRR onlyRADB 667 99% 67
177.53.230.0/24 Valid Other IRR onlyRADB 667 99% 67
186.192.240.0/21 Valid Other IRR onlyRADB 667 99% 67
186.192.240.0/22 Valid Other IRR onlyRADB 667 99% 67
186.192.244.0/22 Valid Other IRR onlyRADB 667 99% 67
186.192.248.0/21 Valid Other IRR onlyRADB 667 99% 67
186.192.248.0/22 Valid Other IRR onlyRADB 667 99% 67
186.192.252.0/22 Valid Other IRR onlyRADB 667 99% 67
2804:140::/32 Valid Other IRR onlyRADB, TC 631 99% 67
177.53.224.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
177.53.225.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
177.53.226.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
177.53.227.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
177.53.228.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
177.53.229.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.240.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.241.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.242.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.243.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.244.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.245.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.246.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.247.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.248.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.250.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.251.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.253.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
186.192.255.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

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

  • Route object: none4
  • Route object: RIR36
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2804:140::/33No route object for it. A route object for 2804:140::/32 with origin AS53138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53138 in the RIR database for the space.631 of 636
Route object: none2804:140:8000::/33No route object for it. A route object for 2804:140::/32 with origin AS53138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53138 in the RIR database for the space.630 of 636
Route object: none186.192.249.0/24No route object for it. A route object for 186.192.248.0/23 with origin AS53138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53138 in the RIR database for the space.2 of 673
Route object: none186.192.252.0/24No route object for it. A route object for 186.192.252.0/23 with origin AS53138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53138 in the RIR database for the space.2 of 673
Route object: RIR177.53.224.0/21Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.53.231.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR186.192.240.0/20Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR186.192.254.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.53.224.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.224.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.226.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.228.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.228.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.230.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.240.0/21Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.240.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.244.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.248.0/21Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.248.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.192.252.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:140::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR177.53.224.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.53.225.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.53.226.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.53.227.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.53.228.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR177.53.229.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.240.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.241.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.242.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.243.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.244.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.245.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.246.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.247.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.248.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.250.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.251.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.253.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR186.192.255.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

177.53.230.0/23RADBValid
186.192.240.0/23RADBValid
186.192.242.0/23RADBValid
186.192.244.0/23RADBValid
186.192.246.0/23RADBValid
186.192.248.0/23RADBValid
186.192.250.0/23RADBValid
186.192.252.0/23RADBValid
186.192.254.0/23RADBValid

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.