Network · data from 2026-11-12
AS10778 MCL Internet
Registry name: AS10778 - MCL Internet, CL · PeeringDB
25IPv4 routes
100.0% RPKI valid · 52.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
12Low visibility
seen by under 10% of full-table peers
30Route objects not announced
registered with origin AS10778, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS10778, 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.
| 200.2.211.0/24 | Valid | Nonecovered by 200.2.208.0/21 | 13 2%low visibility |
| 200.29.1.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.13.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.16.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.20.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.21.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.22.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.25.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.27.0/24 | Valid | Nonecovered by 200.29.0.0/19 | 13 2%low visibility |
| 200.29.68.0/24 | Valid | Nonecovered by 200.29.64.0/19 | 13 2%low visibility |
| 200.29.86.0/24 | Valid | Nonecovered by 200.29.64.0/19 | 13 2%low visibility |
| 200.29.92.0/24 | Valid | Nonecovered by 200.29.64.0/19 | 13 2%low visibility |
| 168.196.184.0/22 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 671 100% |
| 168.196.185.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 168.196.187.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 200.29.6.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.29.70.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.29.12.0/24 | Valid | Other IRR onlyNTTCOM | 665 99% |
| 200.29.14.0/24 | Valid | Other IRR onlyNTTCOM | 110 16% |
| 200.29.65.0/24 | Valid | Other IRR onlyNTTCOM | 110 16% |
| 200.2.192.0/19 | Valid | RIR databaseALTDB, LACNIC, NTTCOM, RADB | 670 100% |
| 200.2.224.0/19 | Valid | RIR databaseALTDB, LACNIC, NTTCOM | 670 100% |
| 200.14.80.0/24 | Valid | RIR databaseALTDB, LACNIC, NTTCOM | 670 100% |
| 200.29.0.0/19 | Valid | RIR databaseALTDB, LACNIC, NTTCOM, RADB | 670 100% |
| 200.29.64.0/19 | Valid | RIR databaseALTDB, LACNIC, NTTCOM, RADB | 670 100% |
AS-SET
AS10778's PeeringDB record names no 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 50 are in fix.csv.
- Route object: none12
- Route object: RIR8
- Route object: not announced30
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.2.211.0/24 | No route object for it. A route object for 200.2.208.0/21 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.1.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.13.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.16.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.20.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.21.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.22.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.25.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.27.0/24 | No route object for it. A route object for 200.29.0.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.68.0/24 | No route object for it. A route object for 200.29.64.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.86.0/24 | No route object for it. A route object for 200.29.64.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: none | 200.29.92.0/24 | No route object for it. A route object for 200.29.64.0/19 with origin AS10778 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10778 in the RIR database for the space. |
| Route object: RIR | 168.196.184.0/22 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.185.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 168.196.187.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.29.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.29.70.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.29.12.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 200.29.14.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 200.29.65.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS10778 whose prefix no peer sees AS10778 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.76.170.0/24 | NTTCOM | No ROA |
| 168.196.184.0/24 | NTTCOM, RADB | Valid |
| 168.196.186.0/24 | NTTCOM | Valid |
| 170.82.128.0/22 | ALTDB | No ROA |
| 170.82.128.0/24 | NTTCOM, RADB | No ROA |
| 170.82.129.0/24 | NTTCOM, RADB | No ROA |
| 170.82.130.0/24 | NTTCOM, RADB | No ROA |
| 170.82.131.0/24 | NTTCOM, RADB | No ROA |
| 200.2.201.0/24 | NTTCOM | Valid |
| 200.2.204.0/23 | RADB | Valid |
| 200.2.206.0/23 | RADB | Valid |
| 200.2.208.0/21 | RADB | Valid |
| 200.2.216.0/22 | RADB | Valid |
| 200.2.226.0/24 | NTTCOM, RADB | Valid |
| 200.2.227.0/24 | NTTCOM | Valid |
| 200.2.228.0/24 | NTTCOM, RADB | Valid |
| 200.2.229.0/24 | NTTCOM | Valid |
| 200.2.230.0/24 | NTTCOM, RADB | Valid |
| 200.2.231.0/24 | NTTCOM, RADB | Valid |
| 200.2.248.0/21 | NTTCOM | Valid |
| 200.2.248.0/24 | NTTCOM, RADB | Valid |
| 200.2.251.0/24 | NTTCOM, RADB | Valid |
| 200.2.252.0/22 | NTTCOM, RADB | Valid |
| 200.2.252.0/23 | RADB | Valid |
| 200.2.253.0/24 | RADB | Valid |
| 200.2.254.0/24 | RADB | Valid |
| 200.2.255.0/24 | RADB | Valid |
| 200.29.72.0/24 | NTTCOM | Valid |
| 2800:8::/32 | LACNIC | Valid |
| 2803:a2c8::/32 | RADB | 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.