Network · data from 2026-11-12
AS44355 Colocation Ltd
Registry name: COLOCATION Colocation Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44355, 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.
| 193.57.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a0f:85c0:2::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0f:85c2:100::/40 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS44355: AS44355:AS-COLOCATION. 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 (AS44355 isn't in the set, or no route object for AS44355 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 | AS44355 in it | Not covered |
|---|---|---|---|---|---|
| AS44355:AS-COLOCATION | RIPElists itself further down14 member sets in no database: AS-202076-OUT, AS-6186, AS-HNSISP-TRANSIT, AS-PBB, AS136346:AS-FASTTNET … | 1,015 | 166 | 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 16 are in fix.csv.
- AS-SET: missing member14
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS-202076-OUT; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS-6186; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS-HNSISP-TRANSIT; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS-PBB; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS136346:AS-FASTTNET; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS137609:AS-DCSISPL; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS198663:AS-NEXARUBE; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS203105:AS-FLIMPIE; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS204985:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS205150:AS-IRIBARREM-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS214174:AS-RIPE; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS215281:AS-NORTHEASTHOSTINGLLC; no IRR database read has it. |
| AS-SET: missing member | AS44355:AS-COLOCATION | AS44355:AS-COLOCATION (RIPE) lists AS215281:AS-ORBITALNETWORK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS44355 whose prefix no peer sees AS44355 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:85c0:69::/48 | RIPE | No ROA |
| 2a0f:85c0:400::/48 | 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.