bgpreport

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

11IPv4 routes 36.4% RPKI valid · 0.0% with a route object
19IPv6 routes 0.0% RPKI valid · 0.0% with a route object
26RPKI invalid 24 origin · 2 maxLength
0No ROA 30 with no route object for this origin
28Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS24141, seen from no peer

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 2
2400:9600:1001::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1002::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1003::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1004::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1005::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1006::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1007::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1008::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1009::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:1111::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:2222::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:3333::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:4444::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:5555::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:6666::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:7777::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:8888::/48 Invalid: origin None 2 0%low visibility 2
2400:9600:9999::/48 Invalid: origin None 2 0%low visibility 2
202.136.208.0/24 Invalid: origin Nonecovered by 202.136.208.0/20 1 0%low visibility 1
202.136.209.0/24 Invalid: origin Nonecovered by 202.136.208.0/20 1 0%low visibility 1
202.136.212.0/24 Invalid: origin Nonecovered by 202.136.208.0/20 1 0%low visibility 1
202.136.214.0/24 Invalid: origin Nonecovered by 202.136.208.0/20 1 0%low visibility 1
210.5.155.0/24 Invalid: origin None 1 0%low visibility 1
210.5.144.0/24 Invalid: maxLength None 1 0%low visibility 1
210.5.151.0/24 Invalid: maxLength None 1 0%low visibility 1
203.176.168.0/24 Valid None 673 100% 67
203.176.170.0/24 Valid None 673 100% 67
210.5.144.0/21 Valid Other origin only 46 7%low visibility 24
210.5.150.0/24 Valid None 5 1%low visibility 6

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
ChangePrefix or setDetailFull-table peers
ROA: origin2400:9600:1000::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1000::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1001::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1001::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1002::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1002::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1003::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1003::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1004::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1004::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1005::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1005::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1006::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1006::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1007::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1007::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1008::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1008::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1009::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1009::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:1111::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:1111::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:2222::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:2222::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:3333::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:3333::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:4444::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:4444::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:5555::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:5555::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:6666::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:6666::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:7777::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:7777::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:8888::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:8888::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin2400:9600:9999::/48An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS24141 should announce it, add a ROA for AS24141.2 of 636
Route object: none2400:9600:9999::/48No route object for it. Add a route object with origin AS24141 in the RIR database for the space.2 of 636
ROA: origin202.136.208.0/24ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141.1 of 673
Route object: none202.136.208.0/24No 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.1 of 673
ROA: origin202.136.209.0/24ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141.1 of 673
Route object: none202.136.209.0/24No 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.1 of 673
ROA: origin202.136.212.0/24ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141.1 of 673
Route object: none202.136.212.0/24No 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.1 of 673
ROA: origin202.136.214.0/24ROAs covering it name AS4812, AS17621, not AS24141. If AS24141 should announce it, add a ROA for AS24141.1 of 673
Route object: none202.136.214.0/24No 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.1 of 673
ROA: origin210.5.155.0/24ROAs covering it name AS4812, not AS24141. If AS24141 should announce it, add a ROA for AS24141.1 of 673
Route object: none210.5.155.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.1 of 673
ROA: maxLength210.5.144.0/24ROA 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.1 of 673
Route object: none210.5.144.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.1 of 673
ROA: maxLength210.5.151.0/24ROA 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.1 of 673
Route object: none210.5.151.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.1 of 673
Route object: none203.176.168.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.673 of 673
Route object: none203.176.170.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.673 of 673
Route object: none210.5.144.0/21Route objects for it name AS4812. Add a route object with origin AS24141 in the RIR database for the space.46 of 673
Route object: none210.5.150.0/24No route object for it. Add a route object with origin AS24141 in the RIR database for the space.5 of 673

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/20RADBNo 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.