bgpreport

Network · data from 2026-11-12

AS399138 MICROLINK-CORE - Microlink Network

Registry name: MICROLINK-CORE - Microlink Network, US · not in PeeringDB

58IPv4 routes 46.6% RPKI valid · 62.1% with a route object
0IPv6 routes
12RPKI invalid 12 origin · 0 maxLength
19No ROA 22 with no route object for this origin
16Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS399138, seen from no peer

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 22
68.68.240.0/22 Invalid: origin Other origin only 17 3%low visibility 17
192.225.208.0/22 Invalid: origin Other origin only 7 1%low visibility 7
104.37.196.0/22 Invalid: origin Other origin only 2 0%low visibility 2
192.142.64.0/20 Invalid: origin None 2 0%low visibility 2
192.142.80.0/20 Invalid: origin None 2 0%low visibility 2
192.142.96.0/20 Invalid: origin None 2 0%low visibility 2
192.142.112.0/20 Invalid: origin None 2 0%low visibility 2
192.142.192.0/20 Invalid: origin None 2 0%low visibility 2
192.142.208.0/20 Invalid: origin None 2 0%low visibility 2
192.142.224.0/20 Invalid: origin None 2 0%low visibility 2
192.142.240.0/20 Invalid: origin None 2 0%low visibility 2
45.121.96.0/24 No ROA Nonecovered by 45.121.96.0/22 672 100% 67
45.121.97.0/24 No ROA Nonecovered by 45.121.96.0/22 672 100% 67
45.121.98.0/24 No ROA Nonecovered by 45.121.96.0/22 672 100% 67
45.121.99.0/24 No ROA Nonecovered by 45.121.96.0/22 672 100% 67
200.229.17.0/24 No ROA None 669 99% 67
216.24.222.0/24 No ROA None 330 49% 64
103.61.176.0/24 No ROA None 11 2%low visibility 7
103.61.177.0/24 No ROA None 11 2%low visibility 7
103.61.178.0/24 No ROA None 11 2%low visibility 7
103.61.179.0/24 No ROA None 11 2%low visibility 7
203.21.69.0/24 No ROA RIR databaseAPNIC 672 100% 67
203.21.70.0/23 No ROA RIR databaseAPNIC 672 100% 67
203.25.204.0/23 No ROA RIR databaseAPNIC 672 100% 67
203.25.226.0/24 No ROA RIR databaseAPNIC 672 100% 67
203.55.124.0/22 No ROA RIR databaseAPNIC 672 100% 67
203.55.130.0/24 No ROA RIR databaseAPNIC 672 100% 67
203.56.122.0/24 No ROA RIR databaseAPNIC 672 100% 67
203.56.170.0/24 No ROA RIR databaseAPNIC 672 100% 67
203.56.177.0/24 No ROA RIR databaseAPNIC 672 100% 67
23.246.188.0/22 Valid RIR databaseARIN 673 100% 67
31.133.84.0/22 Valid RIR databaseRIPE 673 100% 67
85.234.160.0/22 Valid RIR databaseRIPE 673 100% 67
85.234.180.0/22 Valid RIR databaseRIPE 673 100% 67
89.191.116.0/22 Valid RIR databaseRIPE 673 100% 67
91.123.72.0/22 Valid RIR databaseRIPE 673 100% 67
103.31.210.0/24 Valid RIR databaseAPNIC 673 100% 66
122.8.112.0/22 Valid RIR databaseAPNIC 673 100% 67
122.8.124.0/22 Valid RIR databaseAPNIC 673 100% 67
142.248.84.0/22 Valid RIR databaseARIN 673 100% 67
142.248.144.0/22 Valid RIR databaseARIN 673 100% 67
142.249.12.0/22 Valid RIR databaseARIN 673 100% 67
169.128.0.0/22 Valid RIR databaseARIN 673 100% 67
169.128.24.0/22 Valid RIR databaseARIN 673 100% 67
169.128.72.0/22 Valid RIR databaseARIN 673 100% 67
169.128.92.0/22 Valid RIR databaseARIN 673 100% 67
169.128.236.0/22 Valid RIR databaseARIN 673 100% 67
204.16.232.0/22 Valid RIR databaseARIN 673 100% 67
216.235.216.0/22 Valid RIR databaseARIN 673 100% 67
217.24.68.0/22 Valid RIR databaseRIPE 673 100% 67
80.174.148.0/22 Valid RIR databaseRIPE 672 100% 67
91.123.76.0/22 Valid RIR databaseRIPE 672 100% 67
155.103.168.0/22 Valid RIR databaseARIN 672 100% 67
155.103.244.0/22 Valid RIR databaseARIN 672 100% 67
74.118.224.0/22 Valid RIR databaseARIN 671 100% 67
80.174.180.0/22 Valid RIR databaseRIPE 671 100% 67
74.80.200.0/22 Valid RIR databaseARIN 668 99% 67

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
ChangePrefix or setDetailFull-table peers
ROA: origin142.248.212.0/22ROAs covering it name AS19695, not AS399138. If AS399138 should announce it, add a ROA for AS399138.30 of 673
Route object: none142.248.212.0/22Route objects for it name AS19695. Add a route object with origin AS399138 in the RIR database for the space.30 of 673
ROA: origin68.68.240.0/22ROAs covering it name AS2914, AS6079, AS9304, AS214432, not AS399138. If AS399138 should announce it, add a ROA for AS399138.17 of 673
Route object: none68.68.240.0/22Route objects for it name AS2914, AS6079, AS9304, AS214432. Add a route object with origin AS399138 in the RIR database for the space.17 of 673
ROA: origin192.225.208.0/22ROAs covering it name AS5650, not AS399138. If AS399138 should announce it, add a ROA for AS399138.7 of 673
Route object: none192.225.208.0/22Route objects for it name AS5650. Add a route object with origin AS399138 in the RIR database for the space.7 of 673
ROA: origin104.37.196.0/22ROAs covering it name AS6079, AS214432, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none104.37.196.0/22Route objects for it name AS6079, AS214432. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.64.0/20ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.64.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.80.0/20ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.80.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.96.0/20ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.96.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.112.0/20ROAs covering it name AS2914, AS3257, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.112.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.192.0/20ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.192.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.208.0/20ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.208.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.224.0/20ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.224.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: origin192.142.240.0/20ROAs covering it name AS2914, AS3257, AS36916, not AS399138. If AS399138 should announce it, add a ROA for AS399138.2 of 673
Route object: none192.142.240.0/20No route object for it. Add a route object with origin AS399138 in the RIR database for the space.2 of 673
ROA: none45.121.96.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
Route object: none45.121.96.0/24No 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.672 of 673
ROA: none45.121.97.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
Route object: none45.121.97.0/24No 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.672 of 673
ROA: none45.121.98.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
Route object: none45.121.98.0/24No 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.672 of 673
ROA: none45.121.99.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
Route object: none45.121.99.0/24No 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.672 of 673
ROA: none200.229.17.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.669 of 673
Route object: none200.229.17.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.669 of 673
ROA: none216.24.222.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.330 of 673
Route object: none216.24.222.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.330 of 673
ROA: none103.61.176.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.11 of 673
Route object: none103.61.176.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.11 of 673
ROA: none103.61.177.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.11 of 673
Route object: none103.61.177.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.11 of 673
ROA: none103.61.178.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.11 of 673
Route object: none103.61.178.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.11 of 673
ROA: none103.61.179.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.11 of 673
Route object: none103.61.179.0/24No route object for it. Add a route object with origin AS399138 in the RIR database for the space.11 of 673
ROA: none203.21.69.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
ROA: none203.21.70.0/23No ROA covers it. Add a ROA for AS399138, maxLength 23.672 of 673
ROA: none203.25.204.0/23No ROA covers it. Add a ROA for AS399138, maxLength 23.672 of 673
ROA: none203.25.226.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
ROA: none203.55.124.0/22No ROA covers it. Add a ROA for AS399138, maxLength 22.672 of 673
ROA: none203.55.130.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
ROA: none203.56.122.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
ROA: none203.56.170.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673
ROA: none203.56.177.0/24No ROA covers it. Add a ROA for AS399138, maxLength 24.672 of 673

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/22APNICNo ROA
124.42.128.0/23APNICNo ROA
124.42.128.0/24APNICNo ROA
124.42.129.0/24APNICNo ROA
124.42.130.0/23APNICNo ROA
124.42.130.0/24APNICNo ROA
124.42.131.0/24APNICNo ROA
124.42.136.0/23APNICNo ROA
124.42.136.0/24APNICNo ROA
124.42.137.0/24APNICNo ROA
124.42.138.0/23APNICNo ROA
124.42.138.0/24APNICNo ROA
124.42.139.0/24APNICNo 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.