Network · data from 2026-11-12
AS42010 ITPS
Registry name: ITPS I.T. PROFESSIONAL SERVICES LIMITED, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42010, 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.28.50.0/24 | Valid | Nonecovered by 5.28.48.0/21 | 672 100% |
| 91.103.189.0/24 | Valid | Nonecovered by 91.103.188.0/22 | 672 100% |
| 128.65.103.0/24 | Valid | Nonecovered by 128.65.100.0/22 | 672 100% |
| 185.135.170.0/23 | Valid | Nonecovered by 185.135.168.0/22 | 672 100% |
| 193.8.242.0/24 | Valid | Nonecovered by 193.8.240.0/22 | 672 100% |
| 5.28.48.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 91.103.188.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 128.65.96.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.91.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.91.22.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.135.168.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 193.8.240.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 91.103.184.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 2a03:7f80::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS42010: AS-ITPS. 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 (AS42010 isn't in the set, or no route object for AS42010 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 | AS42010 in it | Not covered |
|---|---|---|---|---|---|
| AS-ITPS | RIPE | 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 15 are in fix.csv.
- Route object: none5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.28.50.0/24 | No route object for it. A route object for 5.28.48.0/21 with origin AS42010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42010 in the RIR database for the space. |
| Route object: none | 91.103.189.0/24 | No route object for it. A route object for 91.103.188.0/22 with origin AS42010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42010 in the RIR database for the space. |
| Route object: none | 128.65.103.0/24 | No route object for it. A route object for 128.65.100.0/22 with origin AS42010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42010 in the RIR database for the space. |
| Route object: none | 185.135.170.0/23 | No route object for it. A route object for 185.135.168.0/22 with origin AS42010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42010 in the RIR database for the space. |
| Route object: none | 193.8.242.0/24 | No route object for it. A route object for 193.8.240.0/22 with origin AS42010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42010 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS42010 whose prefix no peer sees AS42010 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.28.48.0/24 | RIPE | Valid |
| 5.28.55.0/24 | RIPE | Valid |
| 5.175.56.0/23 | RIPE | Valid |
| 5.175.58.0/24 | RIPE | Valid |
| 128.65.96.0/24 | RIPE | Valid |
| 128.65.97.0/24 | RIPE | Valid |
| 128.65.98.0/23 | RIPE | Valid |
| 128.65.100.0/22 | RIPE | Valid |
| 185.135.168.0/22 | RIPE | No ROA |
| 193.8.240.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.