Network · data from 2026-11-12
AS151412 Gmax AS151412
Registry name: GMTL-AS-AP - Gmax, BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS151412, 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.89.26.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.100.234.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.186.57.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS151412: AS150748:AS-GMAX. 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 (AS151412 isn't in the set, or no route object for AS151412 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 | AS151412 in it | Not covered |
|---|---|---|---|---|---|
| AS150748:AS-GMAX | APNIC | 1,693 | 3 | Yes | 3 |
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 6 are in fix.csv.
- ROA: origin3
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.89.26.0/24 | ROAs covering it name AS134806, AS150748, not AS151412. If AS151412 should announce it, add a ROA for AS151412. |
| Route object: none | 103.89.26.0/24 | Route objects for it name AS134806, AS150748. Add a route object with origin AS151412 in the RIR database for the space. |
| ROA: origin | 103.100.234.0/24 | ROAs covering it name AS59239, AS134806, AS139013, AS150748, not AS151412. If AS151412 should announce it, add a ROA for AS151412. |
| Route object: none | 103.100.234.0/24 | Route objects for it name AS150748. Add a route object with origin AS151412 in the RIR database for the space. |
| ROA: origin | 103.186.57.0/24 | ROAs covering it name AS59239, AS150748, not AS151412. If AS151412 should announce it, add a ROA for AS151412. |
| Route object: none | 103.186.57.0/24 | Route objects for it name AS59239, AS150748. Add a route object with origin AS151412 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS151412 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.