Network · data from 2026-11-12
AS31726 Telefiber
Registry name: TELEFIBER Telefiber AS, NO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31726, 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.
| 185.149.16.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 185.155.212.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 109.109.80.0/21 | Valid | Nonecovered by 109.109.64.0/19 | 122 18% |
| 109.109.88.0/23 | Valid | Nonecovered by 109.109.64.0/19 | 120 18% |
| 109.109.91.0/24 | Valid | Nonecovered by 109.109.64.0/19 | 120 18% |
| 109.109.93.0/24 | Valid | Nonecovered by 109.109.64.0/19 | 120 18% |
| 109.109.94.0/24 | Valid | Nonecovered by 109.109.64.0/19 | 120 18% |
| 31.204.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.228.48.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 77.95.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 94.139.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 109.109.64.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 185.90.180.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.102.28.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.117.192.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.211.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.229.228.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:1680::/32 | Valid | RIR databaseRIPE | 633 100% |
| 2a06:2240::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a06:8600::/29 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS31726: AS-TF. 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 (AS31726 isn't in the set, or no route object for AS31726 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 | AS31726 in it | Not covered |
|---|---|---|---|---|---|
| AS-TF | RIPE | 9 | 4 | 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 7 are in fix.csv.
- ROA: none2
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.149.16.0/22 | No ROA covers it. Add a ROA for AS31726, maxLength 22. |
| ROA: none | 185.155.212.0/22 | No ROA covers it. Add a ROA for AS31726, maxLength 22. |
| Route object: none | 109.109.80.0/21 | No route object for it. A route object for 109.109.64.0/19 with origin AS31726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31726 in the RIR database for the space. |
| Route object: none | 109.109.88.0/23 | No route object for it. A route object for 109.109.64.0/19 with origin AS31726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31726 in the RIR database for the space. |
| Route object: none | 109.109.91.0/24 | No route object for it. A route object for 109.109.64.0/19 with origin AS31726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31726 in the RIR database for the space. |
| Route object: none | 109.109.93.0/24 | No route object for it. A route object for 109.109.64.0/19 with origin AS31726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31726 in the RIR database for the space. |
| Route object: none | 109.109.94.0/24 | No route object for it. A route object for 109.109.64.0/19 with origin AS31726 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31726 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS31726 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.