Network · data from 2026-11-12
AS133647 RGCM
Registry name: ELXIREDATA-AS-IN - ELXIRE, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133647, 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.
| 43.230.156.0/24 | No ROA | Nonecovered by 43.230.156.0/23 | 11 2%low visibility |
| 43.230.157.0/24 | No ROA | Nonecovered by 43.230.156.0/23 | 11 2%low visibility |
| 43.230.158.0/24 | No ROA | Nonecovered by 43.230.158.0/23 | 11 2%low visibility |
| 43.230.159.0/24 | No ROA | Nonecovered by 43.230.158.0/23 | 11 2%low visibility |
| 103.43.4.0/24 | No ROA | None | 6 1%low visibility |
| 103.43.5.0/24 | No ROA | None | 6 1%low visibility |
| 103.43.6.0/24 | No ROA | None | 6 1%low visibility |
| 103.43.7.0/24 | No ROA | None | 6 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS133647: AS133647:AS-ELXIREDATA. 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 (AS133647 isn't in the set, or no route object for AS133647 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 | AS133647 in it | Not covered |
|---|---|---|---|---|---|
| AS133647:AS-ELXIREDATA | APNIClists itself further down | 38 | 3 | Yes | 4 |
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 44 are in fix.csv.
- ROA: none8
- Route object: none8
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 43.230.156.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 43.230.156.0/24 | No route object for it. A route object for 43.230.156.0/23 with origin AS133647 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 43.230.157.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 43.230.157.0/24 | No route object for it. A route object for 43.230.156.0/23 with origin AS133647 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 43.230.158.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 43.230.158.0/24 | No route object for it. A route object for 43.230.158.0/23 with origin AS133647 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 43.230.159.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 43.230.159.0/24 | No route object for it. A route object for 43.230.158.0/23 with origin AS133647 covers it (filters allowing more-specifics accept it). Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 103.43.4.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 103.43.4.0/24 | No route object for it. Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 103.43.5.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 103.43.5.0/24 | No route object for it. Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 103.43.6.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 103.43.6.0/24 | No route object for it. Add a route object with origin AS133647 in the RIR database for the space. |
| ROA: none | 103.43.7.0/24 | No ROA covers it. Add a ROA for AS133647, maxLength 24. |
| Route object: none | 103.43.7.0/24 | No route object for it. Add a route object with origin AS133647 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133647 whose prefix no peer sees AS133647 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.230.156.0/23 | APNIC | No ROA |
| 43.230.158.0/23 | APNIC | No ROA |
| 45.115.176.0/22 | APNIC | No ROA |
| 45.115.177.0/24 | APNIC | Invalid: origin |
| 45.115.178.0/24 | APNIC | Invalid: origin |
| 45.115.179.0/24 | APNIC | Invalid: origin |
| 103.46.236.0/24 | APNIC | Invalid: origin |
| 103.46.237.0/24 | APNIC | Invalid: origin |
| 103.46.238.0/24 | APNIC | Invalid: origin |
| 103.46.239.0/24 | APNIC | Invalid: origin |
| 103.156.168.0/23 | APNIC | No ROA |
| 103.156.168.0/24 | APNIC | Invalid: origin |
| 103.156.169.0/24 | APNIC | Invalid: origin |
| 103.161.232.0/24 | APNIC | Invalid: origin |
| 103.161.233.0/24 | APNIC | Invalid: origin |
| 103.163.8.0/24 | APNIC | Invalid: origin |
| 103.163.100.0/24 | APNIC | Invalid: origin |
| 103.199.112.0/24 | APNIC | Invalid: origin |
| 103.199.113.0/24 | APNIC | Invalid: origin |
| 103.220.28.0/24 | APNIC | Invalid: origin |
| 103.220.29.0/24 | APNIC | Invalid: origin |
| 103.220.30.0/24 | APNIC | Invalid: origin |
| 103.220.31.0/24 | APNIC | Invalid: origin |
| 2001:df0:dc80::/50 | APNIC | Invalid: origin |
| 2001:df0:dc80:4000::/50 | APNIC | Invalid: origin |
| 2001:df0:dc80:8000::/50 | APNIC | Invalid: origin |
| 2001:df0:dc80:c000::/50 | APNIC | Invalid: origin |
| 2001:df1:64c0::/48 | APNIC | Invalid: origin |
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.