Network · data from 2026-11-12
AS149749 Morizt ID
Registry name: MORIZT-ID - Morizt ID, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149749, 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.189.110.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 2001:df0:d540::/48 | Valid | Other IRR onlyRADB | 635 100% |
| 103.189.111.0/24 | Valid | Other IRR onlyRADB | 36 5%low visibility |
| 103.189.110.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
AS-SET
PeeringDB's irr_as_set for AS149749: AS149749:AS-MORIZT-ID. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS149749 isn't in the set, or no route object for AS149749 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS149749 in it | Not covered |
|---|---|---|---|---|---|
| AS149749:AS-MORIZT-ID | APNIC | 4 | 1 | Yes | 0 |
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 4 are in fix.csv.
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.189.110.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df0:d540::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.189.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.189.110.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS149749 is announced.
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.