Network · data from 2026-11-12
AS3598 MICROSOFT-CORP-AS - Microsoft Corporation
Registry name: MICROSOFT-CORP-AS - Microsoft Corporation, US · not in PeeringDB
18IPv4 routes
88.9% RPKI valid · 100.0% with a route object
5IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
2No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
31Route objects not announced
registered with origin AS3598, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS3598, 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.
| 167.220.0.0/16 | No ROA | Other IRR onlyRADB | 672 100% |
| 167.220.224.0/19 | No ROA | Other IRR onlyRADB | 672 100% |
| 65.53.0.0/16 | Valid | Other IRR onlyRADB | 673 100% |
| 157.54.0.0/16 | Valid | Other IRR onlyRADB | 673 100% |
| 157.57.0.0/16 | Valid | Other IRR onlyRADB | 673 100% |
| 157.59.0.0/16 | Valid | Other IRR onlyRADB | 673 100% |
| 157.60.0.0/16 | Valid | Other IRR onlyRADB | 673 100% |
| 167.220.204.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 167.220.208.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 131.107.0.0/16 | Valid | Other IRR onlyRADB | 672 100% |
| 157.58.0.0/16 | Valid | Other IRR onlyRADB | 672 100% |
| 157.58.192.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 167.220.0.0/17 | Valid | Other IRR onlyRADB | 672 100% |
| 167.220.128.0/18 | Valid | Other IRR onlyRADB | 672 100% |
| 167.220.192.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 194.69.96.0/19 | Valid | Other IRR onlyRADB | 672 100% |
| 198.105.232.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 2001:4898::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 194.69.100.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a01:110:8068::/48 | Valid | RIR databaseRADB, RIPE | 636 100% |
| 2404:f801::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 2a01:110::/32 | Valid | RIR databaseRADB, RIPE | 635 100% |
| 2a01:110:8020::/48 | Valid | RIR databaseRADB, RIPE | 634 100% |
AS-SET
AS3598 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 51 are in fix.csv.
- ROA: none2
- Route object: RIR18
- Route object: not announced31
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.220.0.0/16 | No ROA covers it. Add a ROA for AS3598, maxLength 16. |
| Route object: RIR | 167.220.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 167.220.224.0/19 | No ROA covers it. Add a ROA for AS3598, maxLength 19. |
| Route object: RIR | 167.220.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 65.53.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.54.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.57.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.59.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.60.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.220.204.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.220.208.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.107.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.58.0.0/16 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.58.192.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.220.0.0/17 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.220.128.0/18 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.220.192.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 194.69.96.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 198.105.232.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:4898::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS3598 whose prefix no peer sees AS3598 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 157.58.31.0/24 | RADB | Valid |
| 167.220.42.0/24 | RADB | Valid |
| 167.220.148.0/22 | RADB | Valid |
| 167.220.152.0/24 | RADB | Valid |
| 167.220.224.0/20 | APNIC | Valid |
| 167.220.236.0/22 | APNIC | Valid |
| 167.220.236.0/23 | APNIC | Valid |
| 167.220.236.0/24 | APNIC | Valid |
| 167.220.237.0/24 | APNIC | Valid |
| 167.220.238.0/23 | APNIC | Valid |
| 167.220.238.0/24 | APNIC | Valid |
| 167.220.239.0/24 | APNIC | Valid |
| 167.220.248.0/21 | APNIC | Valid |
| 167.220.248.0/22 | APNIC | Valid |
| 167.220.248.0/23 | APNIC | Valid |
| 167.220.248.0/24 | APNIC | Valid |
| 167.220.249.0/24 | APNIC | Valid |
| 167.220.250.0/23 | APNIC | Valid |
| 167.220.250.0/24 | APNIC | Valid |
| 167.220.251.0/24 | APNIC | Valid |
| 167.220.252.0/22 | APNIC | Valid |
| 167.220.252.0/23 | APNIC | Valid |
| 167.220.252.0/24 | APNIC | Valid |
| 167.220.253.0/24 | APNIC | Valid |
| 167.220.254.0/23 | APNIC | Valid |
| 167.220.254.0/24 | APNIC | Valid |
| 167.220.255.0/24 | APNIC | Valid |
| 204.182.144.0/24 | RADB | No ROA |
| 2404:f801:8028::/48 | APNIC | Valid |
| 2404:f801:8058::/48 | APNIC | Valid |
| 2404:f801:9000::/48 | APNIC | Valid |
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.