Network · data from 2026-11-12
AS41039 Deutsche Breitbanddienste GmbH
Registry name: DON-FTTH Timer, LLC, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41039, 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.153.176.0/24 | Invalid: maxLength | RIR databaseRIPE | 8 1%low visibility |
| 78.31.178.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 78.31.179.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 5.153.176.0/22 | No ROA | RIR databaseRIPE | 670 100% |
| 5.153.186.0/23 | No ROA | RIR databaseRIPE | 670 100% |
| 92.242.120.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.192.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.203.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.214.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.192.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.153.176.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.178.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.179.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.181.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.184.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.185.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.186.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.153.187.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.96.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.96.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.110.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.111.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.112.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.113.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.114.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.115.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 92.242.127.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.192.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.196.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.208.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.209.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.210.0/23 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.212.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.213.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.215.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.217.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.218.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 195.184.200.0/23 | Valid | RIR databaseRIPE | 110 16% |
| 92.242.96.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.97.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.98.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.120.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.121.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.122.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.123.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.124.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.125.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 92.242.126.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.193.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.194.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.195.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.198.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.199.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.200.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.201.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.202.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.204.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.205.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.206.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.207.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.210.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.211.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.219.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.220.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.221.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.222.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
| 195.184.223.0/24 | Valid | RIR databaseRIPE | 18 3%low visibility |
AS-SET
AS41039's PeeringDB record names no AS-SET.
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 14 are in fix.csv.
- ROA: maxLength1
- ROA: none4
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 5.153.176.0/24 | ROA 5.153.176.0/23 AS41039 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 5.153.176.0/24. |
| ROA: none | 78.31.178.0/24 | No ROA covers it. Add a ROA for AS41039, maxLength 24. |
| ROA: none | 78.31.179.0/24 | No ROA covers it. Add a ROA for AS41039, maxLength 24. |
| ROA: none | 5.153.176.0/22 | No ROA covers it. Add a ROA for AS41039, maxLength 22. |
| ROA: none | 5.153.186.0/23 | No ROA covers it. Add a ROA for AS41039, maxLength 23. |
Route objects not announced
Route objects with origin AS41039 whose prefix no peer sees AS41039 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.153.177.0/24 | RIPE | Invalid: maxLength |
| 92.242.99.0/24 | RIPE | Valid |
| 92.242.110.0/23 | RIPE | Valid |
| 92.242.112.0/22 | RIPE | Valid |
| 195.184.196.0/24 | RIPE | Valid |
| 195.184.197.0/24 | RIPE | Valid |
| 195.184.208.0/20 | RIPE | Valid |
| 195.184.216.0/24 | RIPE | Valid |
| 195.184.220.0/22 | RIPE | 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.