Network · data from 2026-11-12
AS131957 MicroAd - MicroAd, Inc.
Registry name: MicroAd - MicroAd, Inc., JP · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131957, 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.
| 103.142.124.0/23 | Valid | Other IRR onlyJPIRR | 672 100% |
| 103.142.125.0/24 | Valid | Other IRR onlyJPIRR | 672 100% |
| 202.233.84.0/22 | Valid | Other IRR onlyJPIRR | 672 100% |
| 202.233.86.0/23 | Valid | Other IRR onlyJPIRR | 672 100% |
| 202.233.84.0/23 | Valid | Other IRR onlyJPIRR | 669 99% |
| 2405:3840::/32 | Valid | Other IRR onlyJPIRR | 636 100% |
AS-SET
AS131957 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 7 are in fix.csv.
- Route object: RIR6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.142.124.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 103.142.125.0/24 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.233.84.0/22 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.233.86.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 202.233.84.0/23 | Route object only in JPIRR. Add it in the RIR database for the space. |
| Route object: RIR | 2405:3840::/32 | Route object only in JPIRR. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131957 whose prefix no peer sees AS131957 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.142.124.0/24 | JPIRR | 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.