Network · data from 2026-11-12
AS399138 MICROLINK-CORE - Microlink Network
Registry name: MICROLINK-CORE - Microlink Network, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS399138, 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.
| 142.248.212.0/22 | Invalid: origin | Other origin only | 30 4%low visibility |
| 68.68.240.0/22 | Invalid: origin | Other origin only | 17 3%low visibility |
| 192.225.208.0/22 | Invalid: origin | Other origin only | 7 1%low visibility |
| 104.37.196.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 192.142.64.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.80.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.96.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.112.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.192.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.208.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.224.0/20 | Invalid: origin | None | 2 0%low visibility |
| 192.142.240.0/20 | Invalid: origin | None | 2 0%low visibility |
| 45.121.96.0/24 | No ROA | Nonecovered by 45.121.96.0/22 | 672 100% |
| 45.121.97.0/24 | No ROA | Nonecovered by 45.121.96.0/22 | 672 100% |
| 45.121.98.0/24 | No ROA | Nonecovered by 45.121.96.0/22 | 672 100% |
| 45.121.99.0/24 | No ROA | Nonecovered by 45.121.96.0/22 | 672 100% |
| 200.229.17.0/24 | No ROA | None | 669 99% |
| 216.24.222.0/24 | No ROA | None | 330 49% |
| 103.61.176.0/24 | No ROA | None | 11 2%low visibility |
| 103.61.177.0/24 | No ROA | None | 11 2%low visibility |
| 103.61.178.0/24 | No ROA | None | 11 2%low visibility |
| 103.61.179.0/24 | No ROA | None | 11 2%low visibility |
| 203.21.69.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.21.70.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.25.204.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.25.226.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.55.124.0/22 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.55.130.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.56.122.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.56.170.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.56.177.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 23.246.188.0/22 | Valid | RIR databaseARIN | 673 100% |
| 31.133.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.234.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.234.180.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.191.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.123.72.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 103.31.210.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 122.8.112.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 122.8.124.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 142.248.84.0/22 | Valid | RIR databaseARIN | 673 100% |
| 142.248.144.0/22 | Valid | RIR databaseARIN | 673 100% |
| 142.249.12.0/22 | Valid | RIR databaseARIN | 673 100% |
| 169.128.0.0/22 | Valid | RIR databaseARIN | 673 100% |
| 169.128.24.0/22 | Valid | RIR databaseARIN | 673 100% |
| 169.128.72.0/22 | Valid | RIR databaseARIN | 673 100% |
| 169.128.92.0/22 | Valid | RIR databaseARIN | 673 100% |
| 169.128.236.0/22 | Valid | RIR databaseARIN | 673 100% |
| 204.16.232.0/22 | Valid | RIR databaseARIN | 673 100% |
| 216.235.216.0/22 | Valid | RIR databaseARIN | 673 100% |
| 217.24.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 80.174.148.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 91.123.76.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 155.103.168.0/22 | Valid | RIR databaseARIN | 672 100% |
| 155.103.244.0/22 | Valid | RIR databaseARIN | 672 100% |
| 74.118.224.0/22 | Valid | RIR databaseARIN | 671 100% |
| 80.174.180.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 74.80.200.0/22 | Valid | RIR databaseARIN | 668 99% |
AS-SET
AS399138 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 66 are in fix.csv.
- ROA: origin12
- ROA: none19
- Route object: none22
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 142.248.212.0/22 | ROAs covering it name AS19695, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 142.248.212.0/22 | Route objects for it name AS19695. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 68.68.240.0/22 | ROAs covering it name AS2914, AS6079, AS9304, AS214432, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 68.68.240.0/22 | Route objects for it name AS2914, AS6079, AS9304, AS214432. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.225.208.0/22 | ROAs covering it name AS5650, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.225.208.0/22 | Route objects for it name AS5650. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 104.37.196.0/22 | ROAs covering it name AS6079, AS214432, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 104.37.196.0/22 | Route objects for it name AS6079, AS214432. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.64.0/20 | ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.64.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.80.0/20 | ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.80.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.96.0/20 | ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.96.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.112.0/20 | ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.112.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.192.0/20 | ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.192.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.208.0/20 | ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.208.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.224.0/20 | ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.224.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: origin | 192.142.240.0/20 | ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138. |
| Route object: none | 192.142.240.0/20 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 45.121.96.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 45.121.96.0/24 | No route object for it. A route object for 45.121.96.0/22 with origin AS399138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 45.121.97.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 45.121.97.0/24 | No route object for it. A route object for 45.121.96.0/22 with origin AS399138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 45.121.98.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 45.121.98.0/24 | No route object for it. A route object for 45.121.96.0/22 with origin AS399138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 45.121.99.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 45.121.99.0/24 | No route object for it. A route object for 45.121.96.0/22 with origin AS399138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 200.229.17.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 200.229.17.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 216.24.222.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 216.24.222.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 103.61.176.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 103.61.176.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 103.61.177.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 103.61.177.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 103.61.178.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 103.61.178.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 103.61.179.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| Route object: none | 103.61.179.0/24 | No route object for it. Add a route object with origin AS399138 in the RIR database for the space. |
| ROA: none | 203.21.69.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| ROA: none | 203.21.70.0/23 | No ROA covers it. Add a ROA for AS399138, maxLength 23. |
| ROA: none | 203.25.204.0/23 | No ROA covers it. Add a ROA for AS399138, maxLength 23. |
| ROA: none | 203.25.226.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| ROA: none | 203.55.124.0/22 | No ROA covers it. Add a ROA for AS399138, maxLength 22. |
| ROA: none | 203.55.130.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| ROA: none | 203.56.122.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| ROA: none | 203.56.170.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
| ROA: none | 203.56.177.0/24 | No ROA covers it. Add a ROA for AS399138, maxLength 24. |
Route objects not announced
Route objects with origin AS399138 whose prefix no peer sees AS399138 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.121.96.0/22 | APNIC | No ROA |
| 124.42.128.0/23 | APNIC | No ROA |
| 124.42.128.0/24 | APNIC | No ROA |
| 124.42.129.0/24 | APNIC | No ROA |
| 124.42.130.0/23 | APNIC | No ROA |
| 124.42.130.0/24 | APNIC | No ROA |
| 124.42.131.0/24 | APNIC | No ROA |
| 124.42.136.0/23 | APNIC | No ROA |
| 124.42.136.0/24 | APNIC | No ROA |
| 124.42.137.0/24 | APNIC | No ROA |
| 124.42.138.0/23 | APNIC | No ROA |
| 124.42.138.0/24 | APNIC | No ROA |
| 124.42.139.0/24 | APNIC | 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.