bgpreport

Network · data from 2026-11-12

AS136180 IPIP-CN

Registry name: IPIP-CN - Beijing Tiantexin Tech. Co., Ltd., CN · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
40Route objects not announced registered with origin AS136180, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136180, 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.203.56.0/24 Valid RIR databaseAPNIC 672 100% 66
103.203.57.0/24 Valid RIR databaseAPNIC 672 100% 66
103.203.59.0/24 Valid RIR databaseAPNIC 671 100% 67
116.213.45.0/24 Valid RIR databaseAPNIC 671 100% 66
103.203.58.0/24 Valid RIR databaseAPNIC 665 99% 67

AS-SET

AS136180'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 40 are in fix.csv.

  • Route object: not announced40

Route objects not announced

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

103.203.56.0/22APNIC, RADBValid
103.203.56.0/23APNICValid
103.203.58.0/23APNICValid
116.213.44.0/22APNIC, RADBValid
116.213.44.0/23APNICValid
116.213.44.0/24APNICValid
116.213.46.0/23APNICValid
116.213.46.0/24APNICValid
116.213.47.0/24APNICValid
2400:87c0::/32APNICValid
2400:87c0::/33APNICValid
2400:87c0::/34APNICValid
2400:87c0::/35APNICValid
2400:87c0::/36APNICValid
2400:87c0:1000::/36APNICValid
2400:87c0:2000::/35APNICValid
2400:87c0:2000::/36APNICValid
2400:87c0:3000::/36APNICValid
2400:87c0:4000::/34APNICValid
2400:87c0:4000::/35APNICValid
2400:87c0:4000::/36APNICValid
2400:87c0:5000::/36APNICValid
2400:87c0:6000::/35APNICValid
2400:87c0:6000::/36APNICValid
2400:87c0:7000::/36APNICValid
2400:87c0:8000::/33APNICValid
2400:87c0:8000::/34APNICValid
2400:87c0:8000::/35APNICValid
2400:87c0:8000::/36APNICValid
2400:87c0:9000::/36APNICValid
2400:87c0:a000::/35APNICValid
2400:87c0:a000::/36APNICValid
2400:87c0:b000::/36APNICValid
2400:87c0:c000::/34APNICValid
2400:87c0:c000::/35APNICValid
2400:87c0:c000::/36APNICValid
2400:87c0:d000::/36APNICValid
2400:87c0:e000::/35APNICValid
2400:87c0:e000::/36APNICValid
2400:87c0:f000::/36APNICValid

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.