Network · data from 2026-11-12
AS59507 terralink networks
Registry name: TLN-AS terralink networks GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59507, 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.
| 5.159.57.194/32 | No ROA | Nonecovered by 5.159.56.0/21 | 2 0%low visibility |
| 5.159.57.195/32 | No ROA | Nonecovered by 5.159.56.0/21 | 2 0%low visibility |
| 5.159.56.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 5.159.72.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.88.244.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 2a04:79c0::/29 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS59507: AS-TLN. 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 (AS59507 isn't in the set, or no route object for AS59507 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 | AS59507 in it | Not covered |
|---|---|---|---|---|---|
| AS-TLN | RIPE | 7 | 2 | Yes | 2 |
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 8 are in fix.csv.
- ROA: none6
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.159.57.194/32 | No ROA covers it. Add a ROA for AS59507, maxLength 32. |
| Route object: none | 5.159.57.194/32 | No route object for it. A route object for 5.159.56.0/21 with origin AS59507 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59507 in the RIR database for the space. |
| ROA: none | 5.159.57.195/32 | No ROA covers it. Add a ROA for AS59507, maxLength 32. |
| Route object: none | 5.159.57.195/32 | No route object for it. A route object for 5.159.56.0/21 with origin AS59507 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59507 in the RIR database for the space. |
| ROA: none | 5.159.56.0/21 | No ROA covers it. Add a ROA for AS59507, maxLength 21. |
| ROA: none | 5.159.72.0/22 | No ROA covers it. Add a ROA for AS59507, maxLength 22. |
| ROA: none | 185.88.244.0/22 | No ROA covers it. Add a ROA for AS59507, maxLength 22. |
| ROA: none | 2a04:79c0::/29 | No ROA covers it. Add a ROA for AS59507, maxLength 29. |
Route objects not announced
Every route object with origin AS59507 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.