bgpreport

Network · data from 2026-11-12

AS53125 Giga+ Fibra - Litoral Norte - SP

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53125, 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.
187.108.112.0/21 Valid Other IRR onlyALTDB 671 100% 67
187.108.116.0/22 Valid Other IRR onlyALTDB 671 100% 67
187.108.120.0/21 Valid Other IRR onlyALTDB 671 100% 67
187.108.120.0/22 Valid Other IRR onlyALTDB 671 100% 67
187.108.124.0/22 Valid Other IRR onlyALTDB 671 100% 67
187.108.112.0/22 Valid Other IRR onlyALTDB 670 100% 67
2804:27cc::/33 Valid Other IRR onlyALTDB 636 100% 67
2804:27cc:8000::/33 Valid Other IRR onlyALTDB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS53125: AS-BSCOSTA. 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 (AS53125 isn't in the set, or no route object for AS53125 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 objectsAS53125 in itNot covered
AS-BSCOSTA ALTDB 1110 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 10 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR187.108.112.0/21Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.108.116.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.108.120.0/21Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.108.120.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.108.124.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.108.112.0/22Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:27cc::/33Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:27cc:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

187.108.112.0/20ALTDBNo ROA
2804:27cc::/32ALTDB, RADBNo 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.