Network · data from 2026-11-12
AS37599 Teraco Data Environments
Registry name: Teraco Data Environments (PTY) LTD - Teraco Data Environments (PTY) LTD, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37599, 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.
| 102.220.103.0/24 | Valid | Nonecovered by 102.220.102.0/23 | 671 100% |
| 102.220.102.0/24 | Valid | Nonecovered by 102.220.102.0/23 | 669 99% |
| 2001:43f8:3e0::/48 | Valid | Nonecovered by 2001:43f8:3e0::/44 | 635 100% |
| 2001:43f8:3e1::/48 | Valid | Nonecovered by 2001:43f8:3e0::/44 | 635 100% |
| 102.220.102.0/23 | Valid | RIR databaseAFRINIC | 669 99% |
| 196.10.98.0/23 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 669 99% |
| 196.10.98.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 669 99% |
| 196.10.99.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS37599: AS-TERACO. 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 (AS37599 isn't in the set, or no route object for AS37599 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 | AS37599 in it | Not covered |
|---|---|---|---|---|---|
| AS-TERACO | AFRINIC3 member sets in no database: AS328242:AS-ALL, AS328568:AS-ITEAM, AS329578:AS-URBANX-ZA | 276 | 86 | 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 8 are in fix.csv.
- Route object: none4
- AS-SET: missing member3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.220.103.0/24 | No route object for it. A route object for 102.220.102.0/23 with origin AS37599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37599 in the RIR database for the space. |
| Route object: none | 102.220.102.0/24 | No route object for it. A route object for 102.220.102.0/23 with origin AS37599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37599 in the RIR database for the space. |
| Route object: none | 2001:43f8:3e0::/48 | No route object for it. A route object for 2001:43f8:3e0::/44 with origin AS37599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37599 in the RIR database for the space. |
| Route object: none | 2001:43f8:3e1::/48 | No route object for it. A route object for 2001:43f8:3e0::/44 with origin AS37599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37599 in the RIR database for the space. |
| AS-SET: missing member | AS-TERACO | AS-TERACO (AFRINIC) lists AS328242:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-TERACO | AS-TERACO (AFRINIC) lists AS328568:AS-ITEAM; no IRR database read has it. |
| AS-SET: missing member | AS-TERACO | AS-TERACO (AFRINIC) lists AS329578:AS-URBANX-ZA; no IRR database read has it. |
Route objects not announced
Route objects with origin AS37599 whose prefix no peer sees AS37599 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:43f8:3e0::/44 | AFRINIC, 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.