Network · data from 2026-11-12
AS24141 DMTNET - Shanghai DMT Information Network cor.,LTD.
Registry name: DMTNET - Shanghai DMT Information Network cor.,LTD., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24141, 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.
| 2400:9600:1000::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1001::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1002::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1003::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1004::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1005::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1006::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1007::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1008::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1009::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:1111::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:2222::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:3333::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:4444::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:5555::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:6666::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:7777::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:8888::/48 | Invalid: origin | None | 2 0%low visibility |
| 2400:9600:9999::/48 | Invalid: origin | None | 2 0%low visibility |
| 202.136.208.0/24 | Invalid: origin | Nonecovered by 202.136.208.0/20 | 1 0%low visibility |
| 202.136.209.0/24 | Invalid: origin | Nonecovered by 202.136.208.0/20 | 1 0%low visibility |
| 202.136.212.0/24 | Invalid: origin | Nonecovered by 202.136.208.0/20 | 1 0%low visibility |
| 202.136.214.0/24 | Invalid: origin | Nonecovered by 202.136.208.0/20 | 1 0%low visibility |
| 210.5.155.0/24 | Invalid: origin | None | 1 0%low visibility |
| 210.5.144.0/24 | Invalid: maxLength | None | 1 0%low visibility |
| 210.5.151.0/24 | Invalid: maxLength | None | 1 0%low visibility |
| 203.176.168.0/24 | Valid | None | 673 100% |
| 203.176.170.0/24 | Valid | None | 673 100% |
| 210.5.144.0/21 | Valid | Other origin only | 46 7%low visibility |
| 210.5.150.0/24 | Valid | None | 5 1%low visibility |
AS-SET
AS24141 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 57 are in fix.csv.
- ROA: origin24
- ROA: maxLength2
- Route object: none30
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2400:9600:1000::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1000::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1001::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1001::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1002::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1002::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1003::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1003::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1004::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1004::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1005::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1005::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1006::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1006::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1007::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1007::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1008::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1008::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1009::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1009::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:1111::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:1111::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:2222::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:2222::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:3333::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:3333::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:4444::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:4444::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:5555::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:5555::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:6666::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:6666::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:7777::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:7777::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:8888::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:8888::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 2400:9600:9999::/48 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 2400:9600:9999::/48 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 202.136.208.0/24 | ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 202.136.208.0/24 | No route object for it. A route object for 202.136.208.0/20 with origin AS24141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 202.136.209.0/24 | ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 202.136.209.0/24 | No route object for it. A route object for 202.136.208.0/20 with origin AS24141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 202.136.212.0/24 | ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 202.136.212.0/24 | No route object for it. A route object for 202.136.208.0/20 with origin AS24141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 202.136.214.0/24 | ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 202.136.214.0/24 | No route object for it. A route object for 202.136.208.0/20 with origin AS24141 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: origin | 210.5.155.0/24 | ROAs covering it name AS4812, not AS24141. If AS24141 should announce it, add a ROA for AS24141. |
| Route object: none | 210.5.155.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: maxLength | 210.5.144.0/24 | ROA 210.5.144.0/21 AS24141 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 210.5.144.0/24. |
| Route object: none | 210.5.144.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| ROA: maxLength | 210.5.151.0/24 | ROA 210.5.144.0/21 AS24141 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 210.5.151.0/24. |
| Route object: none | 210.5.151.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| Route object: none | 203.176.168.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| Route object: none | 203.176.170.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
| Route object: none | 210.5.144.0/21 | Route objects for it name AS4812. Add a route object with origin AS24141 in the RIR database for the space. |
| Route object: none | 210.5.150.0/24 | No route object for it. Add a route object with origin AS24141 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24141 whose prefix no peer sees AS24141 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.136.208.0/20 | 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.