bgpreport

Network · data from 2026-11-12

AS272851 GIGA FIBRA

Registry name: AS272851 - GIGA FIBRA SAS, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272851, 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.52.152.0/21 No ROA Other IRR onlyRADB 671 100% 66
186.194.58.0/23 Valid Other IRR onlyRADB 672 100% 66
186.194.58.0/24 Valid Other IRR onlyRADB 672 100% 66
186.194.59.0/24 Valid Other IRR onlyRADB 672 100% 66
186.194.60.0/23 Valid Other IRR onlyRADB 672 100% 66
186.194.60.0/24 Valid Other IRR onlyRADB 672 100% 66
186.194.61.0/24 Valid Other IRR onlyRADB 672 100% 66
187.73.136.0/21 Valid Other IRR onlyRADB 671 100% 66
2803:8290::/33 Valid Other IRR onlyRADB 636 100% 67
2803:8290:100::/44 Valid Other IRR onlyRADB 636 100% 67
2803:8290:200::/48 Valid Other IRR onlyRADB 636 100% 67
2803:8290:8000::/33 Valid Other IRR onlyRADB 636 100% 67
2803:8290:1::/48 Valid Other IRR onlyRADB 325 51% 64
2803:8290:4::/48 Valid Other IRR onlyRADB 325 51% 64
2803:8290:5::/48 Valid Other IRR onlyRADB 325 51% 64
2803:8290:110::/44 Valid Other IRR onlyRADB 325 51% 64
2803:8290:208::/48 Valid Other IRR onlyRADB 325 51% 64
2803:8290:210::/48 Valid Other IRR onlyRADB 325 51% 64
186.194.56.0/24 Valid Other IRR onlyRADB 113 17% 43
186.194.57.0/24 Valid Other IRR onlyRADB 113 17% 43
186.194.62.0/24 Valid Other IRR onlyRADB 113 17% 43
186.194.63.0/24 Valid Other IRR onlyRADB 113 17% 43
186.194.56.0/21 Valid RIR databaseLACNIC, RADB 671 100% 66
201.46.115.0/24 Valid RIR databaseLACNIC, RADB 671 100% 66
2803:8290::/32 Valid RIR databaseLACNIC, RADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS272851: AS-GIGACO. 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 (AS272851 isn't in the set, or no route object for AS272851 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 objectsAS272851 in itNot covered
AS-GIGACO RADB 63157 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 23 are in fix.csv.

  • ROA: none1
  • Route object: RIR22
ChangePrefix or setDetailFull-table peers
ROA: none38.52.152.0/21No ROA covers it. Add a ROA for AS272851, maxLength 21.671 of 673
Route object: RIR38.52.152.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR186.194.58.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.58.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.60.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.60.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.194.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.73.136.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2803:8290::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:8290:100::/44Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:8290:200::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:8290:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2803:8290:1::/48Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR2803:8290:4::/48Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR2803:8290:5::/48Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR2803:8290:110::/44Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR2803:8290:208::/48Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR2803:8290:210::/48Route object only in RADB. Add it in the RIR database for the space.325 of 636
Route object: RIR186.194.56.0/24Route object only in RADB. Add it in the RIR database for the space.113 of 673
Route object: RIR186.194.57.0/24Route object only in RADB. Add it in the RIR database for the space.113 of 673
Route object: RIR186.194.62.0/24Route object only in RADB. Add it in the RIR database for the space.113 of 673
Route object: RIR186.194.63.0/24Route object only in RADB. Add it in the RIR database for the space.113 of 673

Route objects not announced

Every route object with origin AS272851 is announced.

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.