Network · data from 2026-11-12
AS37525 BytesNET
Registry name: Altron TMT (Pty) Ltd - Altron TMT (Pty) Ltd, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37525, 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.
| 41.85.134.0/24 | No ROA | Nonecovered by 41.85.128.0/19 | 671 100% |
| 41.76.56.0/21 | No ROA | Other IRR onlyRIPE-NONAUTH | 671 100% |
| 41.85.128.0/19 | No ROA | Other IRR onlyRIPE-NONAUTH | 671 100% |
| 41.87.224.0/19 | No ROA | Other IRR onlyRIPE-NONAUTH | 671 100% |
| 105.235.160.0/20 | No ROA | Other IRR onlyRIPE-NONAUTH | 671 100% |
| 197.156.0.0/18 | No ROA | Other IRR onlyRIPE-NONAUTH | 671 100% |
| 2c0f:fda0::/32 | No ROA | RIR databaseAFRINIC | 330 52% |
AS-SET
PeeringDB's irr_as_set for AS37525: RS-BYTES. 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 (AS37525 isn't in the set, or no route object for AS37525 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 | AS37525 in it | Not covered | |
|---|---|---|---|---|---|---|
| RS-BYTES | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 14 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: RIR5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 41.85.134.0/24 | No ROA covers it. Add a ROA for AS37525, maxLength 24. |
| Route object: none | 41.85.134.0/24 | No route object for it. A route object for 41.85.128.0/19 with origin AS37525 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37525 in the RIR database for the space. |
| ROA: none | 41.76.56.0/21 | No ROA covers it. Add a ROA for AS37525, maxLength 21. |
| Route object: RIR | 41.76.56.0/21 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.85.128.0/19 | No ROA covers it. Add a ROA for AS37525, maxLength 19. |
| Route object: RIR | 41.85.128.0/19 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.87.224.0/19 | No ROA covers it. Add a ROA for AS37525, maxLength 19. |
| Route object: RIR | 41.87.224.0/19 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 105.235.160.0/20 | No ROA covers it. Add a ROA for AS37525, maxLength 20. |
| Route object: RIR | 105.235.160.0/20 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 197.156.0.0/18 | No ROA covers it. Add a ROA for AS37525, maxLength 18. |
| Route object: RIR | 197.156.0.0/18 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 2c0f:fda0::/32 | No ROA covers it. Add a ROA for AS37525, maxLength 32. |
Route objects not announced
Route objects with origin AS37525 whose prefix no peer sees AS37525 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 196.43.243.0/24 | RIPE-NONAUTH | No ROA |
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.