Network · data from 2026-11-12
AS48896 DHOSTING-AS dhosting.pl Sp. z o.o.
Registry name: DHOSTING-AS dhosting.pl Sp. z o.o., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48896, 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.
| 109.95.152.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 195.88.50.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 195.191.232.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 80.73.250.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 2001:67c:1c8::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 89.124.245.0/24 | No ROA | RIR databaseRIPE | 474 70% |
| 109.95.157.0/24 | No ROA | RIR databaseRIPE | 1 0%low visibility |
| 45.159.81.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.159.82.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.159.83.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS48896 isn't in PeeringDB, where networks name their 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 22 are in fix.csv.
- ROA: none7
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.95.152.0/21 | No ROA covers it. Add a ROA for AS48896, maxLength 21. |
| ROA: none | 195.88.50.0/23 | No ROA covers it. Add a ROA for AS48896, maxLength 23. |
| ROA: none | 195.191.232.0/23 | No ROA covers it. Add a ROA for AS48896, maxLength 23. |
| ROA: none | 80.73.250.0/24 | No ROA covers it. Add a ROA for AS48896, maxLength 24. |
| ROA: none | 2001:67c:1c8::/48 | No ROA covers it. Add a ROA for AS48896, maxLength 48. |
| ROA: none | 89.124.245.0/24 | No ROA covers it. Add a ROA for AS48896, maxLength 24. |
| ROA: none | 109.95.157.0/24 | No ROA covers it. Add a ROA for AS48896, maxLength 24. |
Route objects not announced
Route objects with origin AS48896 whose prefix no peer sees AS48896 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.95.152.0/23 | RIPE | No ROA |
| 109.95.152.0/24 | RIPE | No ROA |
| 109.95.153.0/24 | RIPE | No ROA |
| 109.95.154.0/23 | RIPE | No ROA |
| 109.95.154.0/24 | RIPE | No ROA |
| 109.95.155.0/24 | RIPE | No ROA |
| 109.95.156.0/22 | RIPE | No ROA |
| 109.95.156.0/24 | RIPE | No ROA |
| 109.95.158.0/24 | RIPE | No ROA |
| 109.95.159.0/24 | RIPE | No ROA |
| 195.85.85.0/24 | ARIN | Valid |
| 195.88.50.0/24 | RIPE | No ROA |
| 195.88.51.0/24 | RIPE | No ROA |
| 195.191.232.0/24 | RIPE | No ROA |
| 195.191.233.0/24 | RIPE | No ROA |
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.