Network · data from 2026-11-12
AS49835 Fundació Guifi.net
Registry name: GUIFINET-AS Fundacio Privada per a la Xarxa Lliure, Oberta i Neutral, guifi.net, ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49835, 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.
| 149.6.204.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 167.160.15.0/24 | Valid | Other origin only | 673 100% |
| 5.10.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.10.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.10.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.10.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.10.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.10.205.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.10.206.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.10.207.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.9.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.10.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.11.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.12.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.13.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.69.15.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.32.16.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.32.17.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.32.18.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.32.19.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a00:1508::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS49835: AS-GUIFINET. 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 (AS49835 isn't in the set, or no route object for AS49835 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 | AS49835 in it | Not covered |
|---|---|---|---|---|---|
| AS-GUIFINET | RIPE | 17 | 1 | Yes | 1 |
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.
- ROA: none1
- Route object: none1
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.6.204.0/24 | No ROA covers it. Add a ROA for AS49835, maxLength 24. |
| Route object: RIR | 149.6.204.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 167.160.15.0/24 | Route objects for it name AS206565. Add a route object with origin AS49835 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49835 whose prefix no peer sees AS49835 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.10.200.0/21 | RIPE | No ROA |
| 109.69.8.0/21 | RIPE | No ROA |
| 109.69.14.0/24 | RIPE | Valid |
| 149.6.203.0/24 | RIPE-NONAUTH | No ROA |
| 185.32.16.0/22 | RIPE | No ROA |
| 2a00:1508:6400::/39 | RIPE | Invalid: maxLength |
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.