bgpreport

Network · data from 2026-11-12

AS52613 Giga+ Fibra - SP

Registry name: AS52613 - GIGA MAIS FIBRA TELECOMUNICACOES S.A., BR · PeeringDB

26IPv4 routes 96.2% RPKI valid · 96.2% with a route object
15IPv6 routes 100.0% RPKI valid · 93.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS52613, seen from no peer

Announced routes

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

38.250.204.0/23 No ROA Nonecovered by 38.250.204.0/22 672 100% 67
2804:d3c:300::/40 Valid Nonecovered by 2804:d3c::/32 305 48% 62
143.0.56.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 671 100% 67
170.231.232.0/22 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
177.125.168.0/21 Valid Other IRR onlyNTTCOM 671 100% 67
138.36.56.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 670 100% 67
143.0.56.0/23 Valid Other IRR onlyRADB 670 100% 67
143.0.58.0/23 Valid Other IRR onlyRADB 670 100% 67
168.232.160.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 670 100% 67
2804:d3c::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:d3c:100::/40 Valid Other IRR onlyRADB 636 100% 67
2804:d3c:600::/40 Valid Other IRR onlyRADB 636 100% 67
2804:d3c:8000::/48 Valid Other IRR onlyRADB 636 100% 67
2804:d3c:3::/48 Valid Other IRR onlyRADB 355 56% 65
2804:d3c:200::/40 Valid Other IRR onlyRADB 355 56% 65
2804:d3c:2::/48 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:4::/48 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:5::/48 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:6::/48 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:7::/48 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:400::/40 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:500::/40 Valid Other IRR onlyRADB 354 56% 65
2804:d3c:8100::/44 Valid Other IRR onlyRADB 354 56% 65
177.125.172.0/22 Valid Other IRR onlyTC 205 30% 56
138.36.57.0/24 Valid Other IRR onlyRADB 127 19% 44
138.36.59.0/24 Valid Other IRR onlyRADB 127 19% 44
170.231.232.0/23 Valid Other IRR onlyRADB 127 19% 44
177.125.171.0/24 Valid Other IRR onlyRADB 127 19% 44
177.125.175.0/24 Valid Other IRR onlyRADB 127 19% 44
138.36.56.0/24 Valid Other IRR onlyRADB 126 19% 44
138.36.58.0/24 Valid Other IRR onlyRADB 126 19% 44
170.231.234.0/23 Valid Other IRR onlyRADB 126 19% 44
177.125.172.0/24 Valid Other IRR onlyRADB 126 19% 44
177.125.174.0/24 Valid Other IRR onlyRADB 126 19% 44
138.36.56.0/23 Valid Other IRR onlyRADB 98 15% 37
138.36.58.0/23 Valid Other IRR onlyRADB 98 15% 37
168.232.160.0/23 Valid Other IRR onlyRADB 98 15% 37
168.232.162.0/23 Valid Other IRR onlyRADB 98 15% 37
177.125.170.0/23 Valid Other IRR onlyRADB 98 15% 37
177.125.172.0/23 Valid Other IRR onlyRADB 98 15% 37
177.125.174.0/23 Valid Other IRR onlyRADB 98 15% 37

AS-SET

AS52613's PeeringDB record names no AS-SET.

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

  • ROA: none1
  • Route object: none2
  • Route object: RIR39
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none38.250.204.0/23No ROA covers it. Add a ROA for AS52613, maxLength 23.672 of 673
Route object: none38.250.204.0/23No route object for it. A route object for 38.250.204.0/22 with origin AS52613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52613 in the RIR database for the space.672 of 673
Route object: none2804:d3c:300::/40No route object for it. A route object for 2804:d3c::/32 with origin AS52613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52613 in the RIR database for the space.305 of 636
Route object: RIR143.0.56.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.231.232.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.125.168.0/21Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR138.36.56.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR143.0.56.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR143.0.58.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR168.232.160.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:d3c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:d3c:100::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:d3c:600::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:d3c:8000::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:d3c:3::/48Route object only in RADB. Add it in the RIR database for the space.355 of 636
Route object: RIR2804:d3c:200::/40Route object only in RADB. Add it in the RIR database for the space.355 of 636
Route object: RIR2804:d3c:2::/48Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:4::/48Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:5::/48Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:6::/48Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:7::/48Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:400::/40Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:500::/40Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR2804:d3c:8100::/44Route object only in RADB. Add it in the RIR database for the space.354 of 636
Route object: RIR177.125.172.0/22Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR138.36.57.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR138.36.59.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR170.231.232.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR177.125.171.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR177.125.175.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
Route object: RIR138.36.56.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR138.36.58.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR170.231.234.0/23Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR177.125.172.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR177.125.174.0/24Route object only in RADB. Add it in the RIR database for the space.126 of 673
Route object: RIR138.36.56.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR138.36.58.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR168.232.160.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR168.232.162.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR177.125.170.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR177.125.172.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673
Route object: RIR177.125.174.0/23Route object only in RADB. Add it in the RIR database for the space.98 of 673

Route objects not announced

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

38.250.200.0/21RADBNo ROA
38.250.204.0/22NTTCOM, RADBNo ROA
45.7.16.0/22NTTCOMNo ROA
45.170.200.0/22NTTCOMNo ROA
45.190.212.0/22NTTCOMNo ROA
143.0.188.0/22NTTCOMNo ROA
170.83.36.0/22NTTCOMNo ROA
177.125.168.0/22RADBValid
177.125.168.0/24RADBValid
177.125.169.0/24RADBValid
177.125.170.0/24RADBValid
181.191.60.0/22NTTCOMNo 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.