Network · data from 2026-11-12
AS263189 GLG PERU SAC
Registry name: AS263189 - GLG PERU SAC, PE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263189, 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.
| 2803:4480:6000::/48 | Valid | Nonecovered by 2803:4480::/32 | 636 100% |
| 2803:4480:7000::/48 | Valid | Nonecovered by 2803:4480::/32 | 636 100% |
| 2803:4480:7002::/48 | Valid | Nonecovered by 2803:4480::/32 | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS263189: AS263189. 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 (AS263189 isn't in the set, or no route object for AS263189 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.
| Name | Database | ASNs | Sets | AS263189 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS263189 | A single AS number, not a set: AS263189 (this network), 8 route objects. | |||||
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 11 are in fix.csv.
- Route object: none3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:4480:6000::/48 | No route object for it. A route object for 2803:4480::/32 with origin AS263189 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263189 in the RIR database for the space. |
| Route object: none | 2803:4480:7000::/48 | No route object for it. A route object for 2803:4480::/32 with origin AS263189 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263189 in the RIR database for the space. |
| Route object: none | 2803:4480:7002::/48 | No route object for it. A route object for 2803:4480::/32 with origin AS263189 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263189 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS263189 whose prefix no peer sees AS263189 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.10.104.0/22 | RADB | No ROA |
| 38.226.24.0/22 | RADB | No ROA |
| 45.177.196.0/23 | LACNIC | Valid |
| 45.177.196.0/24 | RADB | Valid |
| 179.43.96.0/22 | LACNIC, RADB | Valid |
| 179.43.99.0/24 | LACNIC | Valid |
| 2803:3a60::/32 | LACNIC | Valid |
| 2803:4480::/32 | LACNIC | Valid |
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.