bgpreport

Network · data from 2026-11-12

AS13537 MEGACOLO - Mega Colocation, Inc.

Registry name: MEGACOLO - Mega Colocation, Inc., US · not in PeeringDB

47IPv4 routes 68.1% RPKI valid · 66.0% with a route object
0IPv6 routes
15RPKI invalid 15 origin · 0 maxLength
0No ROA 16 with no route object for this origin
17Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS13537, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13537, 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.

45.153.166.0/24 Invalid: origin Other origin only 2 0%low visibility 2
83.245.9.0/24 Invalid: origin Other origin only 2 0%low visibility 2
163.5.200.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.92.135.0/24 Invalid: origin None 2 0%low visibility 2
178.92.157.0/24 Invalid: origin None 2 0%low visibility 2
62.105.197.0/24 Invalid: origin Other origin only 1 0%low visibility 1
82.108.127.0/24 Invalid: origin Other origin only 1 0%low visibility 1
89.30.139.0/24 Invalid: origin None 1 0%low visibility 1
143.20.136.0/24 Invalid: origin Other origin only 1 0%low visibility 1
151.247.3.0/24 Invalid: origin Other origin only 1 0%low visibility 1
151.247.107.0/24 Invalid: origin Other origin only 1 0%low visibility 1
164.37.203.0/24 Invalid: origin Other origin only 1 0%low visibility 1
168.222.80.0/24 Invalid: origin Other origin only 1 0%low visibility 1
194.122.81.0/24 Invalid: origin Other origin only 1 0%low visibility 1
195.40.158.0/24 Invalid: origin Other origin only 1 0%low visibility 1
82.153.115.0/24 Valid None 1 0%low visibility 1
213.210.53.0/24 Valid Other IRR onlyRADB 671 100% 67
78.154.127.0/24 Valid Other IRR onlyRADB 668 99% 66
82.109.242.0/24 Valid Other IRR onlyRADB 668 99% 66
82.119.204.0/24 Valid Other IRR onlyRADB 668 99% 66
212.180.127.0/24 Valid Other IRR onlyRADB 668 99% 66
212.189.121.0/24 Valid Other IRR onlyRADB 668 99% 66
87.82.217.0/24 Valid Other IRR onlyRADB 667 99% 66
64.81.168.0/24 Valid RIR databaseARIN, RADB 671 100% 67
89.23.92.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
95.134.5.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
109.121.40.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
141.11.57.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
82.47.49.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
85.92.141.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
110.172.189.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
192.25.213.0/24 Valid RIR databaseARIN, RADB 669 99% 67
212.212.27.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
77.105.10.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
84.247.114.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
87.82.62.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
89.149.63.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
109.66.160.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
114.69.247.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
186.241.161.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
201.50.24.0/24 Valid RIR databaseRADB, RIPE 668 99% 66
45.86.243.0/24 Valid RIR databaseRADB, RIPE 667 99% 66
82.110.224.0/24 Valid RIR databaseRADB, RIPE 667 99% 66
87.86.18.0/24 Valid RIR databaseRADB, RIPE 667 99% 66
104.234.232.0/24 Valid RIR databaseARIN, RADB 667 99% 66
192.48.151.0/24 Valid RIR databaseARIN, RADB 667 99% 66
87.232.106.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

AS13537 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 49 are in fix.csv.

  • ROA: origin15
  • Route object: none16
  • Route object: RIR7
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: origin45.153.166.0/24ROAs covering it name AS136809, AS214962, not AS13537. If AS13537 should announce it, add a ROA for AS13537.2 of 673
Route object: none45.153.166.0/24Route objects for it name AS136809, AS214962. Add a route object with origin AS13537 in the RIR database for the space.2 of 673
ROA: origin83.245.9.0/24ROAs covering it name AS834, AS3257, not AS13537. If AS13537 should announce it, add a ROA for AS13537.2 of 673
Route object: none83.245.9.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.2 of 673
ROA: origin163.5.200.0/24ROAs covering it name AS197170, not AS13537. If AS13537 should announce it, add a ROA for AS13537.2 of 673
Route object: none163.5.200.0/24Route objects for it name AS197170. Add a route object with origin AS13537 in the RIR database for the space.2 of 673
ROA: origin178.92.135.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.2 of 673
Route object: none178.92.135.0/24No route object for it. Add a route object with origin AS13537 in the RIR database for the space.2 of 673
ROA: origin178.92.157.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.2 of 673
Route object: none178.92.157.0/24No route object for it. Add a route object with origin AS13537 in the RIR database for the space.2 of 673
ROA: origin62.105.197.0/24ROAs covering it name AS134494, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none62.105.197.0/24Route objects for it name AS134494. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin82.108.127.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none82.108.127.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin89.30.139.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none89.30.139.0/24No route object for it. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin143.20.136.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none143.20.136.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin151.247.3.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none151.247.3.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin151.247.107.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none151.247.107.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin164.37.203.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none164.37.203.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin168.222.80.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none168.222.80.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin194.122.81.0/24ROAs covering it name AS3257, AS9033, AS36040, AS134494, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none194.122.81.0/24Route objects for it name AS134494. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
ROA: origin195.40.158.0/24ROAs covering it name AS834, not AS13537. If AS13537 should announce it, add a ROA for AS13537.1 of 673
Route object: none195.40.158.0/24Route objects for it name AS834. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
Route object: none82.153.115.0/24No route object for it. Add a route object with origin AS13537 in the RIR database for the space.1 of 673
Route object: RIR213.210.53.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR78.154.127.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR82.109.242.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR82.119.204.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR212.180.127.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR212.189.121.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR87.82.217.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

Route objects with origin AS13537 whose prefix no peer sees AS13537 announce. Many are kept on purpose (backup routes, space announced only in some places).

67.213.112.0/20ALTDBNo ROA
84.75.84.0/24RADB, RIPEValid
85.189.36.0/24RADB, RIPEValid
92.112.229.0/24RADB, RIPEValid
107.149.200.0/24ARIN, RADBValid
143.14.209.0/24RADB, RIPEValid
178.239.122.0/24RADB, RIPEValid
188.220.84.0/24RADB, RIPEValid
194.61.236.0/24RADB, RIPEValid
195.72.169.0/24RADB, RIPEValid
195.78.56.0/24ARIN, RADBValid

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.