bgpreport

Network · data from 2026-11-12

AS30031 MIMECAST-US - Mimecast North America Inc

Registry name: MIMECAST-US - Mimecast North America Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30031, 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.

63.128.21.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.139.110.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.139.111.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.211.30.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.205.24.0/24 No ROA Other IRR onlyRADB 673 100% 67
41.74.203.0/24 No ROA Other IRR onlyRADB 200 30% 38
170.10.140.0/24 Valid None 672 100% 67
170.10.150.0/24 Valid Other IRR onlyRADB 673 100% 67
170.10.151.0/24 Valid Other IRR onlyRADB 673 100% 67
170.10.152.0/24 Valid Other IRR onlyRADB 673 100% 67
170.10.153.0/24 Valid Other IRR onlyRADB 673 100% 67
2620:134:6008::/48 Valid Other IRR onlyRADB 635 100% 68
2620:134:6009::/48 Valid Other IRR onlyRADB 635 100% 68
2620:134:6002::/48 Valid Other IRR onlyRADB 634 100% 68
170.10.142.0/24 Valid Other IRR onlyRADB 121 18% 33
170.10.128.0/23 Valid RIR databaseARIN, RADB 673 100% 67
170.10.130.0/24 Valid RIR databaseARIN, RADB 673 100% 67
170.10.131.0/24 Valid RIR databaseARIN, RADB 673 100% 67
170.10.132.0/23 Valid RIR databaseARIN, RADB 673 100% 67
170.10.156.0/24 Valid RIR databaseARIN, RADB 673 100% 67
170.10.157.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.145.219.0/24 Valid RIR databaseARIN, RADB 673 100% 67
2620:134:6001::/48 Valid RIR databaseARIN 635 100% 68
2620:134:6000::/48 Valid RIR databaseARIN, RADB 634 100% 68
216.145.218.0/24 Valid RIR databaseARIN, RADB 200 30% 40
216.145.222.0/24 Valid RIR databaseARIN, RADB 200 30% 40

AS-SET

AS30031 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 31 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR14
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none63.128.21.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.673 of 673
Route object: RIR63.128.21.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.139.110.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.673 of 673
Route object: RIR205.139.110.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.139.111.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.673 of 673
Route object: RIR205.139.111.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.211.30.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.673 of 673
Route object: RIR207.211.30.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.205.24.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.673 of 673
Route object: RIR216.205.24.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.74.203.0/24No ROA covers it. Add a ROA for AS30031, maxLength 24.200 of 673
Route object: RIR41.74.203.0/24Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: none170.10.140.0/24No route object for it. Add a route object with origin AS30031 in the RIR database for the space.672 of 673
Route object: RIR170.10.150.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.10.151.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.10.152.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.10.153.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2620:134:6008::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2620:134:6009::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2620:134:6002::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR170.10.142.0/24Route object only in RADB. Add it in the RIR database for the space.121 of 673

Route objects not announced

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

147.28.39.0/24RIPEInvalid: origin
170.10.150.0/23RADBNo ROA
170.10.152.0/23RADBNo ROA
170.10.154.0/24RADBNo ROA
170.10.155.0/24RADBNo ROA
193.7.207.0/24RIPEInvalid: origin
194.104.111.0/24RIPEInvalid: origin
216.145.221.0/24ARIN, RADBValid
2620:134:600b::/48ARINValid
2a02:5be0:9::/48RIPEInvalid: origin

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.