bgpreport

Network · data from 2026-11-12

AS136167 CHINATELECOM-AS-AP - CHINA TELECOM (MACAU) COMPANY LIMITED

Registry name: CHINATELECOM-AS-AP - CHINA TELECOM (MACAU) COMPANY LIMITED, MO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136167, 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.
2001:df5:900::/48 No ROA Other IRR onlyRADB 636 100% 67
2001:df6:4f00::/48 No ROA Other IRR onlyRADB 636 100% 67
203.223.17.0/24 Valid Other IRR onlyRADB 672 100% 66
203.223.19.0/24 Valid Other IRR onlyRADB 672 100% 66
203.223.20.0/24 Valid Other IRR onlyRADB 672 100% 66
203.223.18.0/24 Valid Other IRR onlyRADB 671 100% 66
74.119.65.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
74.119.66.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
74.119.67.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.143.92.0/23 Valid RIR databaseAPNIC 672 100% 66
202.75.248.0/22 Valid RIR databaseAPNIC 672 100% 66
74.119.64.0/21 Valid RIR databaseAPNIC, RADB 671 100% 66
103.143.92.0/24 Valid RIR databaseAPNIC 670 100% 66
103.143.93.0/24 Valid RIR databaseAPNIC 670 100% 66
202.75.250.0/24 Valid RIR databaseAPNIC 670 100% 66
202.75.251.0/24 Valid RIR databaseAPNIC 670 100% 66
2400:9380:90c0::/44 Valid RIR databaseAPNIC 635 100% 69
2400:9380:91c0::/44 Valid RIR databaseAPNIC 635 100% 69
2400:9380:92c0::/44 Valid RIR databaseAPNIC 635 100% 69
2400:9380:93c0::/44 Valid RIR databaseAPNIC 635 100% 69
2400:9380:80c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:81c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:82c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:83c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:84c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:85c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:86c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:87c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:88c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:89c0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8ac0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8bc0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8cc0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8dc0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8ec0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:8fc0::/44 Valid RIR databaseAPNIC, RADB 634 100% 67
2400:9380:94c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:95c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:96c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:97c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:98c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:99c0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9ac0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9bc0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9cc0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9dc0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9ec0::/44 Valid RIR databaseAPNIC 634 100% 68
2400:9380:9fc0::/44 Valid RIR databaseAPNIC 634 100% 68

AS-SET

AS136167 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 16 are in fix.csv.

  • ROA: none2
  • Route object: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2001:df5:900::/48No ROA covers it. Add a ROA for AS136167, maxLength 48.636 of 636
Route object: RIR2001:df5:900::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2001:df6:4f00::/48No ROA covers it. Add a ROA for AS136167, maxLength 48.636 of 636
Route object: RIR2001:df6:4f00::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR203.223.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.223.19.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.223.20.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR203.223.18.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

74.119.64.0/22APNIC, RADBValid
74.119.64.0/24APNIC, RADBValid
74.119.68.0/22APNIC, RADBValid
74.119.68.0/24APNIC, RADBValid
74.119.69.0/24APNIC, RADBValid
74.119.70.0/24APNIC, RADBValid
74.119.71.0/24APNIC, RADBValid
202.75.248.0/23APNICValid

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.