bgpreport

Network · data from 2026-11-12

AS8070 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation

Registry name: MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US · not in PeeringDB

30IPv4 routes 100.0% RPKI valid · 90.0% with a route object
14IPv6 routes 100.0% RPKI valid · 57.1% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 9 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS8070, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS8070, 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.
51.54.0.0/15 Valid None 672 100% 69
57.16.0.0/14 Valid None 672 100% 69
206.41.48.0/24 Valid None 672 100% 69
2601:9200:c001::/48 Valid Nonecovered by 2601:9200:c000::/36 635 100% 69
2601:9200:c003::/48 Valid Nonecovered by 2601:9200:c000::/36 635 100% 69
2601:9200:c004::/48 Valid Nonecovered by 2601:9200:c000::/36 635 100% 69
2607:9240::/48 Valid Nonecovered by 2607:9240::/42 635 100% 69
2607:9240:1::/48 Valid Nonecovered by 2607:9240::/42 635 100% 69
2607:9240:2::/48 Valid Nonecovered by 2607:9240::/42 635 100% 69
20.34.0.0/15 Valid Other IRR onlyRADB 672 100% 69
20.158.0.0/15 Valid Other IRR onlyRADB 672 100% 69
52.126.0.0/15 Valid Other IRR onlyRADB 672 100% 69
131.253.72.0/22 Valid Other IRR onlyRADB 672 100% 69
131.253.80.0/20 Valid Other IRR onlyRADB 672 100% 69
131.253.112.0/21 Valid Other IRR onlyRADB 672 100% 69
131.253.120.0/22 Valid Other IRR onlyRADB 672 100% 69
165.159.132.0/22 Valid Other IRR onlyRADB 672 100% 69
165.159.136.0/22 Valid Other IRR onlyRADB 672 100% 69
165.159.188.0/22 Valid Other IRR onlyRADB 672 100% 69
20.140.0.0/15 Valid Other IRR onlyRADB 669 99% 69
62.10.0.0/15 Valid Other IRR onlyRADB 669 99% 69
204.13.120.0/21 Valid Other IRR onlyRADB 669 99% 69
2001:489a:2000::/35 Valid Other IRR onlyRADB 635 100% 69
2603:1063:300::/40 Valid Other IRR onlyRADB 635 100% 69
2603:1063:2100::/40 Valid Other IRR onlyRADB 635 100% 69
2603:1063:7c00::/38 Valid Other IRR onlyRADB 635 100% 69
2001:489a:4000::/35 Valid Other IRR onlyRADB 632 99% 69
64.40.141.0/24 Valid RIR databaseARIN 672 100% 69
97.107.239.0/24 Valid RIR databaseARIN 672 100% 69
137.70.156.0/24 Valid RIR databaseARIN, RADB 672 100% 69
137.70.158.0/24 Valid RIR databaseARIN, RADB 672 100% 69
152.228.48.0/24 Valid RIR databaseARIN 672 100% 69
152.228.49.0/24 Valid RIR databaseARIN 672 100% 69
170.85.197.0/24 Valid RIR databaseARIN 672 100% 69
170.85.198.0/24 Valid RIR databaseARIN 672 100% 69
195.134.224.0/19 Valid RIR databaseRADB, RIPE 672 100% 69
199.15.136.0/23 Valid RIR databaseARIN, RADB 672 100% 69
199.15.138.0/24 Valid RIR databaseARIN 672 100% 69
199.34.97.0/24 Valid RIR databaseARIN 672 100% 69
208.68.130.0/24 Valid RIR databaseARIN 672 100% 69
208.68.131.0/24 Valid RIR databaseARIN 672 100% 69
2605:4300:3601::/48 Valid RIR databaseARIN 635 100% 69
2606:e540:c02::/48 Valid RIR databaseARIN, RADB 635 100% 69
2606:e540:c03::/48 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

AS8070 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 35 are in fix.csv.

  • Route object: none9
  • Route object: RIR18
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none51.54.0.0/15No route object for it. Add a route object with origin AS8070 in the RIR database for the space.672 of 673
Route object: none57.16.0.0/14No route object for it. Add a route object with origin AS8070 in the RIR database for the space.672 of 673
Route object: none206.41.48.0/24No route object for it. Add a route object with origin AS8070 in the RIR database for the space.672 of 673
Route object: none2601:9200:c001::/48No route object for it. A route object for 2601:9200:c000::/36 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: none2601:9200:c003::/48No route object for it. A route object for 2601:9200:c000::/36 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: none2601:9200:c004::/48No route object for it. A route object for 2601:9200:c000::/36 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: none2607:9240::/48No route object for it. A route object for 2607:9240::/42 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: none2607:9240:1::/48No route object for it. A route object for 2607:9240::/42 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: none2607:9240:2::/48No route object for it. A route object for 2607:9240::/42 with origin AS8070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8070 in the RIR database for the space.635 of 636
Route object: RIR20.34.0.0/15Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR20.158.0.0/15Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR52.126.0.0/15Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.253.72.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.253.80.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.253.112.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR131.253.120.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.159.132.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.159.136.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR165.159.188.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR20.140.0.0/15Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR62.10.0.0/15Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR204.13.120.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2001:489a:2000::/35Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2603:1063:300::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2603:1063:2100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2603:1063:7c00::/38Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2001:489a:4000::/35Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

153.45.148.0/24ARINValid
153.45.149.0/24ARINValid
153.45.172.0/24ARINValid
153.45.173.0/24ARINValid
194.41.17.0/24RADBValid
2601:9200:c000::/36ARINValid
2605:4300:3611::/48ARINValid
2607:9240::/42ARINValid

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.