bgpreport

Network · data from 2026-11-12

AS52712 Connetiva Internet

Registry name: AS52712 - CONECTIVA INFORMATICA E TELECOMUNICACOES LTDA - ME, BR · PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
4IPv6 routes 0.0% RPKI valid · 75.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS52712, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS52712, 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:1c74:b000::/36 No ROA Nonecovered by 2804:1c74:8000::/33 1 0%low visibility 1
131.108.25.0/24 No ROA Other IRR onlyTC 670 100% 67
170.245.144.0/24 No ROA Other IRR onlyTC 670 100% 67
131.108.24.0/22 No ROA Other IRR onlyRADB, TC 664 99% 67
131.108.24.0/24 No ROA Other IRR onlyTC 664 99% 67
177.73.230.0/24 No ROA Other IRR onlyTC 664 99% 67
170.245.144.0/22 No ROA Other IRR onlyRADB, TC 663 99% 67
177.73.228.0/22 No ROA Other IRR onlyRADB, TC 663 99% 67
2804:1c74::/32 No ROA Other IRR onlyRADB, TC 630 99% 69
2804:1c74::/33 No ROA Other IRR onlyRADB, TC 630 99% 69
2804:1c74:8000::/33 No ROA Other IRR onlyRADB, TC 630 99% 69

AS-SET

PeeringDB's irr_as_set for AS52712: AS52712:AS-CUSTOMERS. 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 (AS52712 isn't in the set, or no route object for AS52712 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 objectsAS52712 in itNot covered
AS52712:AS-CUSTOMERS TC 010 No 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 37 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
  • AS-SET: own ASN1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none2804:1c74:b000::/36No ROA covers it. Add a ROA for AS52712, maxLength 36.1 of 636
Route object: none2804:1c74:b000::/36No route object for it. A route object for 2804:1c74:8000::/33 with origin AS52712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52712 in the RIR database for the space.1 of 636
ROA: none131.108.25.0/24No ROA covers it. Add a ROA for AS52712, maxLength 24.670 of 673
Route object: RIR131.108.25.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none170.245.144.0/24No ROA covers it. Add a ROA for AS52712, maxLength 24.670 of 673
Route object: RIR170.245.144.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none131.108.24.0/22No ROA covers it. Add a ROA for AS52712, maxLength 22.664 of 673
Route object: RIR131.108.24.0/22Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
ROA: none131.108.24.0/24No ROA covers it. Add a ROA for AS52712, maxLength 24.664 of 673
Route object: RIR131.108.24.0/24Route object only in TC. Add it in the RIR database for the space.664 of 673
ROA: none177.73.230.0/24No ROA covers it. Add a ROA for AS52712, maxLength 24.664 of 673
Route object: RIR177.73.230.0/24Route object only in TC. Add it in the RIR database for the space.664 of 673
ROA: none170.245.144.0/22No ROA covers it. Add a ROA for AS52712, maxLength 22.663 of 673
Route object: RIR170.245.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
ROA: none177.73.228.0/22No ROA covers it. Add a ROA for AS52712, maxLength 22.663 of 673
Route object: RIR177.73.228.0/22Route object only in RADB, TC. Add it in the RIR database for the space.663 of 673
ROA: none2804:1c74::/32No ROA covers it. Add a ROA for AS52712, maxLength 32.630 of 636
Route object: RIR2804:1c74::/32Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:1c74::/33No ROA covers it. Add a ROA for AS52712, maxLength 33.630 of 636
Route object: RIR2804:1c74::/33Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
ROA: none2804:1c74:8000::/33No ROA covers it. Add a ROA for AS52712, maxLength 33.630 of 636
Route object: RIR2804:1c74:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.630 of 636
AS-SET: own ASNAS52712:AS-CUSTOMERSAS52712 isn't in AS52712:AS-CUSTOMERS (TC) once expanded. Add AS52712 to it.

Route objects not announced

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

131.108.24.0/23RADB, TCNo ROA
131.108.26.0/23TCNo ROA
131.108.26.0/24TCNo ROA
131.108.27.0/24TCNo ROA
170.245.144.0/23RADB, TCNo ROA
170.245.145.0/24TCNo ROA
170.245.146.0/23RADB, TCNo ROA
170.245.146.0/24TCNo ROA
170.245.147.0/24TCNo ROA
177.73.228.0/23RADB, TCNo ROA
177.73.228.0/24TCNo ROA
177.73.229.0/24TCNo ROA
177.73.230.0/23TCNo ROA
177.73.231.0/24TCNo 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.