Network · data from 2026-11-12
AS265303
Not in the RIR AS name list · not in PeeringDB
21IPv4 routes
100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
8Low visibility
seen by under 10% of full-table peers
39Route objects not announced
registered with origin AS265303, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS265303, 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.
| 189.39.216.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 201.87.136.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 201.87.146.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 201.87.147.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 201.87.148.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 200.150.175.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 201.87.152.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 177.126.11.0/24 | Valid | Other IRR onlyRADB | 665 99% |
| 189.39.218.0/23 | Valid | Other IRR onlyRADB | 614 91% |
| 201.87.133.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 298 44% |
| 168.0.172.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 268 40% |
| 201.87.134.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 265 39% |
| 201.87.146.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 265 39% |
| 177.126.1.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 65 10%low visibility |
| 177.126.6.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 65 10%low visibility |
| 201.87.150.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 61 9%low visibility |
| 177.126.10.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
| 177.126.8.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 0 0%low visibility |
| 177.126.10.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 0 0%low visibility |
| 177.126.13.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 0 0%low visibility |
| 177.126.15.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 0 0%low visibility |
AS-SET
AS265303 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 60 are in fix.csv.
- Route object: RIR21
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 189.39.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.136.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.146.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.150.175.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.152.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.39.218.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.133.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.0.172.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.134.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.146.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.1.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.6.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 201.87.150.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.8.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.10.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.13.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.126.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265303 whose prefix no peer sees AS265303 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.0.172.0/23 | RADB | Valid |
| 168.0.172.0/24 | RADB | Valid |
| 168.0.173.0/24 | RADB | Valid |
| 168.0.174.0/23 | RADB | Valid |
| 168.0.174.0/24 | RADB | Valid |
| 168.0.175.0/24 | RADB | Valid |
| 187.120.12.0/24 | NTTCOM, RADB | Valid |
| 189.39.216.0/22 | NTTCOM, RADB | Valid |
| 189.39.216.0/23 | RADB | Valid |
| 189.39.217.0/24 | RADB | Valid |
| 189.39.218.0/24 | RADB | Valid |
| 189.39.219.0/24 | RADB | Valid |
| 200.150.164.0/23 | NTTCOM, RADB | Valid |
| 200.150.164.0/24 | RADB | Valid |
| 200.150.165.0/24 | RADB | Valid |
| 200.150.167.0/24 | NTTCOM, RADB | Valid |
| 200.150.169.0/24 | NTTCOM, RADB | Valid |
| 200.150.170.0/24 | NTTCOM, RADB | Valid |
| 200.150.172.0/24 | NTTCOM, RADB | Valid |
| 200.150.174.0/23 | NTTCOM, RADB | Valid |
| 200.150.174.0/24 | RADB | Valid |
| 201.87.128.0/24 | NTTCOM, RADB | Valid |
| 201.87.131.0/24 | NTTCOM, RADB | Valid |
| 201.87.134.0/24 | RADB | Valid |
| 201.87.135.0/24 | RADB | Valid |
| 201.87.136.0/23 | NTTCOM, RADB | Valid |
| 201.87.137.0/24 | RADB | Valid |
| 201.87.139.0/24 | NTTCOM, RADB | Valid |
| 201.87.140.0/23 | NTTCOM, RADB | Valid |
| 201.87.140.0/24 | RADB | Valid |
| 201.87.141.0/24 | RADB | Valid |
| 201.87.142.0/24 | NTTCOM, RADB | Valid |
| 201.87.144.0/24 | NTTCOM, RADB | Valid |
| 201.87.148.0/23 | NTTCOM, RADB | Valid |
| 201.87.149.0/24 | RADB | Valid |
| 201.87.152.0/23 | NTTCOM, RADB | Valid |
| 201.87.153.0/24 | RADB | Valid |
| 201.87.157.0/24 | NTTCOM, RADB | Valid |
| 2804:2dc8::/32 | NTTCOM, RADB | 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.