bgpreport

Network · data from 2026-11-12

AS10222 Multibyte Info Technology

Registry name: MITL-HK - Multibyte Info Technology Limited, HK · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS10222, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS10222, 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.
103.77.195.0/24 Valid RIR databaseAPNIC 672 100% 67
103.77.192.0/23 Valid RIR databaseAPNIC, RADB 669 99% 66
103.77.192.0/24 Valid RIR databaseAPNIC, REACH 669 99% 66
103.77.193.0/24 Valid RIR databaseAPNIC, REACH 669 99% 66
116.206.208.0/23 Valid RIR databaseAPNIC, RADB 669 99% 66
116.206.208.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
116.206.209.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
116.206.210.0/23 Valid RIR databaseAPNIC, RADB 669 99% 67
116.206.210.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
116.206.211.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
2402:15c0:6::/48 Valid RIR databaseAPNIC, NTTCOM, RADB 631 99% 67
2402:15c0:16::/48 Valid RIR databaseAPNIC 631 99% 67

AS-SET

AS10222'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 20 are in fix.csv.

  • Route object: not announced20

Route objects not announced

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

103.77.194.0/23APNICValid
103.77.194.0/24APNICValid
117.103.40.0/21RADBNo ROA
118.102.36.0/22NTTCOM, RADBNo ROA
118.102.36.0/23NTTCOM, RADBNo ROA
118.102.36.0/24NTTCOM, RADBNo ROA
119.27.128.0/19NTTCOM, RADBNo ROA
119.27.128.0/21RADBNo ROA
119.27.140.0/24NTTCOM, RADBNo ROA
120.143.128.0/22NTTCOM, RADBNo ROA
120.143.136.0/21NTTCOM, RADBNo ROA
120.143.136.0/22NTTCOM, RADBNo ROA
120.143.136.0/23NTTCOM, RADBNo ROA
120.143.136.0/24NTTCOM, RADBNo ROA
2402:15c0::/32NTTCOM, RADBNo ROA
2402:15c0:1::/48APNICValid
2402:15c0:2::/48APNICValid
2402:15c0:3::/48APNICValid
2402:15c0:4::/48APNICValid
2402:15c0:5::/48APNICValid

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.