Network · data from 2026-11-12
AS903 UCT
Registry name: UNIFIED-COMMUNICATIONS-TECHNOLOGIES - Unified Communications Technologies, LLC, US · PeeringDB
19IPv4 routes
100.0% RPKI valid · 21.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
15 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS903, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS903, 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.
| 155.103.224.0/23 | Valid | Nonecovered by 155.103.224.0/22 | 667 99% |
| 209.112.92.0/24 | Valid | Nonecovered by 209.112.92.0/22 | 667 99% |
| 209.112.93.0/24 | Valid | Nonecovered by 209.112.92.0/22 | 667 99% |
| 209.112.94.0/24 | Valid | Nonecovered by 209.112.92.0/22 | 667 99% |
| 209.112.95.0/24 | Valid | Nonecovered by 209.112.92.0/22 | 667 99% |
| 209.141.16.0/24 | Valid | Nonecovered by 209.141.16.0/22 | 667 99% |
| 209.141.17.0/24 | Valid | Nonecovered by 209.141.16.0/22 | 667 99% |
| 209.141.18.0/24 | Valid | Nonecovered by 209.141.16.0/22 | 667 99% |
| 209.141.19.0/24 | Valid | Nonecovered by 209.141.16.0/22 | 667 99% |
| 209.141.20.0/23 | Valid | Nonecovered by 209.141.20.0/22 | 667 99% |
| 209.141.21.0/24 | Valid | Nonecovered by 209.141.20.0/22 | 667 99% |
| 209.141.22.0/24 | Valid | Nonecovered by 209.141.20.0/22 | 667 99% |
| 155.103.224.0/24 | Valid | Nonecovered by 155.103.224.0/22 | 664 99% |
| 155.103.225.0/24 | Valid | Nonecovered by 155.103.224.0/22 | 664 99% |
| 209.141.20.0/24 | Valid | Nonecovered by 209.141.20.0/22 | 664 99% |
| 209.112.92.0/22 | Valid | Other IRR onlyRADB | 664 99% |
| 209.141.16.0/22 | Valid | RIR databaseARIN, RADB | 664 99% |
| 209.141.20.0/22 | Valid | RIR databaseARIN, RADB | 664 99% |
| 155.103.224.0/22 | Valid | RIR databaseARIN, RADB | 2 0%low visibility |
AS-SET
AS903'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 24 are in fix.csv.
- Route object: none15
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 155.103.224.0/23 | No route object for it. A route object for 155.103.224.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.112.92.0/24 | No route object for it. A route object for 209.112.92.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.112.93.0/24 | No route object for it. A route object for 209.112.92.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.112.94.0/24 | No route object for it. A route object for 209.112.92.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.112.95.0/24 | No route object for it. A route object for 209.112.92.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.16.0/24 | No route object for it. A route object for 209.141.16.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.17.0/24 | No route object for it. A route object for 209.141.16.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.18.0/24 | No route object for it. A route object for 209.141.16.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.19.0/24 | No route object for it. A route object for 209.141.16.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.20.0/23 | No route object for it. A route object for 209.141.20.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.21.0/24 | No route object for it. A route object for 209.141.20.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.22.0/24 | No route object for it. A route object for 209.141.20.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 155.103.224.0/24 | No route object for it. A route object for 155.103.224.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 155.103.225.0/24 | No route object for it. A route object for 155.103.224.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: none | 209.141.20.0/24 | No route object for it. A route object for 209.141.20.0/22 with origin AS903 covers it (filters allowing more-specifics accept it). Add a route object with origin AS903 in the RIR database for the space. |
| Route object: RIR | 209.112.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS903 whose prefix no peer sees AS903 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.128.112.0/24 | RADB | Invalid: origin |
| 38.128.113.0/24 | RADB | Invalid: origin |
| 38.128.114.0/24 | RADB | Invalid: origin |
| 38.128.115.0/24 | RADB | Invalid: origin |
| 38.128.116.0/24 | RADB | Invalid: origin |
| 38.128.117.0/24 | RADB | Invalid: origin |
| 38.128.118.0/24 | RADB | Invalid: origin |
| 38.128.119.0/24 | RADB | Invalid: origin |
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.