Network · data from 2026-11-12
AS269989 FIBERNET Guatemala
Registry name: AS269989 - FIBERNET S.A, GT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269989, 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:bee0::/36 | Valid | Nonecovered by 2803:bee0::/32 | 635 100% |
| 2803:bee0:8100::/40 | Valid | Nonecovered by 2803:bee0::/32 | 371 58% |
| 2803:bee0:8400::/41 | Valid | Nonecovered by 2803:bee0::/32 | 371 58% |
| 2803:bee0:8480::/42 | Valid | Nonecovered by 2803:bee0::/32 | 371 58% |
| 138.117.231.0/24 | Valid | Other IRR onlyRADB | 662 98% |
| 138.117.230.0/24 | Valid | Other IRR onlyRADB | 658 98% |
| 138.117.228.0/24 | Valid | RIR databaseLACNIC, RADB | 662 98% |
| 2803:bee0::/32 | Valid | RIR databaseLACNIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS269989: AS269989:AS-CARRIER. 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 (AS269989 isn't in the set, or no route object for AS269989 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 | AS269989 in it | Not covered |
|---|---|---|---|---|---|
| AS269989:AS-CARRIER | LACNIC | 1 | 1 | No | 8 |
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 9 are in fix.csv.
- Route object: none4
- Route object: RIR2
- AS-SET: own ASN1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2803:bee0::/36 | No route object for it. A route object for 2803:bee0::/32 with origin AS269989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269989 in the RIR database for the space. |
| Route object: none | 2803:bee0:8100::/40 | No route object for it. A route object for 2803:bee0::/32 with origin AS269989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269989 in the RIR database for the space. |
| Route object: none | 2803:bee0:8400::/41 | No route object for it. A route object for 2803:bee0::/32 with origin AS269989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269989 in the RIR database for the space. |
| Route object: none | 2803:bee0:8480::/42 | No route object for it. A route object for 2803:bee0::/32 with origin AS269989 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269989 in the RIR database for the space. |
| Route object: RIR | 138.117.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.117.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS269989:AS-CARRIER | AS269989 isn't in AS269989:AS-CARRIER (LACNIC) once expanded. Add AS269989 to it. |
Route objects not announced
Route objects with origin AS269989 whose prefix no peer sees AS269989 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.117.228.0/22 | RADB | No ROA |
| 138.117.230.0/23 | 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.