Network · data from 2026-11-12
AS9115 Hostopia, a HostPapa, Inc. company [Europe]
Registry name: INFB-AS9115 Hostpapa UK Ltd., GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9115, 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.
| 207.55.255.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 91.136.0.0/24 | Valid | Nonecovered by 91.136.0.0/17 | 673 100% |
| 91.136.125.0/24 | Valid | Nonecovered by 91.136.0.0/17 | 673 100% |
| 2a01:7f60:20::/44 | Valid | Nonecovered by 2a01:7f60::/32 | 635 100% |
| 91.136.0.0/17 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:7f60::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS9115: ARIN::AS-HOSTOPIA. 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 (AS9115 isn't in the set, or no route object for AS9115 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 | AS9115 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-HOSTOPIA | ARIN | 6 | 1 | 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: none1
- Route object: none3
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 207.55.255.0/24 | No ROA covers it. Add a ROA for AS9115, maxLength 24. |
| Route object: RIR | 207.55.255.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: none | 91.136.0.0/24 | No route object for it. A route object for 91.136.0.0/17 with origin AS9115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9115 in the RIR database for the space. |
| Route object: none | 91.136.125.0/24 | No route object for it. A route object for 91.136.0.0/17 with origin AS9115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9115 in the RIR database for the space. |
| Route object: none | 2a01:7f60:20::/44 | No route object for it. A route object for 2a01:7f60::/32 with origin AS9115 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9115 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9115 whose prefix no peer sees AS9115 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.136.126.0/23 | RIPE | Valid |
| 216.55.135.0/24 | RIPE-NONAUTH | 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.