Network · data from 2026-11-12
AS8431 AS8431 TEA Ltd.
Registry name: AS8431 TEA Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8431, 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.
| 195.230.16.0/23 | Valid | Nonecovered by 195.230.16.0/20 | 673 100% |
| 195.230.0.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.4.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.6.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.7.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.230.18.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS8431 isn't in PeeringDB, where networks name their AS-SET.
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 9 are in fix.csv.
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 195.230.16.0/23 | No route object for it. A route object for 195.230.16.0/20 with origin AS8431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8431 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS8431 whose prefix no peer sees AS8431 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.230.0.0/19 | RIPE | No ROA |
| 195.230.8.0/24 | RIPE | Valid |
| 195.230.9.0/24 | RIPE | Valid |
| 195.230.10.0/23 | RIPE | Valid |
| 195.230.12.0/22 | RIPE | Valid |
| 195.230.13.0/24 | RIPE | Valid |
| 195.230.14.0/24 | RIPE | Valid |
| 195.230.16.0/20 | RIPE | 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.