bgpreport

Network · data from 2026-11-12

AS136792 Mimecast Australia Pty Ltd

Registry name: MIMECAST-AS-AP - Mimecast Australia Pty Ltd, AU · PeeringDB

12IPv4 routes 91.7% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS136792, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136792, 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.
41.74.203.0/24 No ROA Other IRR onlyNTTCOM 46 7%low visibility 17
103.13.69.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
180.189.28.0/24 Valid Other IRR onlyNTTCOM 671 100% 67
170.10.142.0/24 Valid Other IRR onlyNTTCOM, RADB 34 5%low visibility 9
103.96.22.0/24 Valid RIR databaseAPNIC 672 100% 67
103.96.23.0/24 Valid RIR databaseAPNIC 672 100% 67
170.10.134.0/24 Valid RIR databaseARIN, NTTCOM, RADB 672 100% 67
170.10.135.0/24 Valid RIR databaseARIN, RADB 672 100% 67
103.96.20.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.96.21.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
2401:73c0::/48 Valid RIR databaseAPNIC, NTTCOM 636 100% 69
2401:73c0:1::/48 Valid RIR databaseAPNIC, RADB 636 100% 69
216.145.218.0/24 Valid RIR databaseARIN, NTTCOM, RADB 32 5%low visibility 10
216.145.222.0/24 Valid RIR databaseARIN, NTTCOM, RADB 32 5%low visibility 10

AS-SET

AS136792'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 8 are in fix.csv.

  • ROA: none1
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none41.74.203.0/24No ROA covers it. Add a ROA for AS136792, maxLength 24.46 of 673
Route object: RIR41.74.203.0/24Route object only in NTTCOM. Add it in the RIR database for the space.46 of 673
Route object: RIR103.13.69.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR180.189.28.0/24Route object only in NTTCOM. Add it in the RIR database for the space.671 of 673
Route object: RIR170.10.142.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.34 of 673

Route objects not announced

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

103.96.20.0/22RADBNo ROA
216.145.217.0/24ARIN, NTTCOM, RADBValid
2401:73c0:4::/48APNICValid

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.