Network · data from 2026-11-12
AS202036 EXTREME-COMM EXTREME COMMUNICATIONS TECHNOLOGY LIMITED
Registry name: EXTREME-COMM EXTREME COMMUNICATIONS TECHNOLOGY LIMITED, HK · not in PeeringDB
62IPv4 routes
96.8% RPKI valid · 98.4% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
2No ROA
1 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
15Route objects not announced
registered with origin AS202036, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS202036, 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.
| 204.58.136.0/22 | No ROA | Other IRR onlyALTDB | 671 100% |
| 200.33.58.0/24 | No ROA | Other IRR onlyALTDB | 670 100% |
| 103.181.248.0/24 | Valid | None | 672 100% |
| 45.201.36.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 45.201.40.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 154.83.104.0/21 | Valid | Other IRR onlyRADB | 670 100% |
| 156.225.2.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 156.225.50.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.158.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.159.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.161.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.163.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.168.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.169.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.174.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.181.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.182.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.186.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 156.249.197.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 202.155.64.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 23.157.236.0/24 | Valid | RIR databaseARIN | 673 100% |
| 151.246.215.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.247.48.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 151.247.82.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 209.131.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.229.118.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 23.160.132.0/24 | Valid | RIR databaseARIN | 671 100% |
| 95.134.81.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 103.14.92.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 103.129.199.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 145.79.83.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 145.79.100.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 145.79.104.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 145.79.111.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 145.79.115.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 145.79.119.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 162.4.57.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 178.95.247.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 45.192.112.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.192.115.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.198.231.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.16.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.17.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.18.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.19.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.20.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.21.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.22.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.23.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.24.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.25.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.28.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.29.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.30.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.31.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 45.201.32.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 103.4.100.0/23 | Valid | RIR databaseAPNIC | 670 100% |
| 103.4.101.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 49.128.222.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 112.196.199.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 112.196.215.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 124.66.221.0/24 | Valid | RIR databaseAPNIC | 667 99% |
AS-SET
AS202036 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 37 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR19
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.58.136.0/22 | No ROA covers it. Add a ROA for AS202036, maxLength 22. |
| Route object: RIR | 204.58.136.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 200.33.58.0/24 | No ROA covers it. Add a ROA for AS202036, maxLength 24. |
| Route object: RIR | 200.33.58.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: none | 103.181.248.0/24 | No route object for it. Add a route object with origin AS202036 in the RIR database for the space. |
| Route object: RIR | 45.201.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.201.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.83.104.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.225.2.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.225.50.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.161.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.163.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.174.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 156.249.197.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.155.64.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202036 whose prefix no peer sees AS202036 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.137.188.0/24 | ARIN | Valid |
| 23.160.28.0/24 | ARIN | Valid |
| 103.4.100.0/24 | APNIC | Valid |
| 103.218.96.0/24 | APNIC | Valid |
| 103.218.97.0/24 | APNIC | Valid |
| 103.218.98.0/24 | APNIC | Valid |
| 103.218.99.0/24 | APNIC | Valid |
| 163.8.204.0/24 | APNIC, RADB | Valid |
| 163.8.206.0/24 | APNIC, RADB | Valid |
| 163.8.208.0/24 | APNIC, RADB | Valid |
| 165.49.232.0/24 | RADB | Valid |
| 165.49.242.0/24 | RADB | Valid |
| 165.49.245.0/24 | RADB | Valid |
| 200.13.72.0/24 | ALTDB | No ROA |
| 200.34.24.0/22 | ALTDB | 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.