Network · data from 2026-11-12
AS29534 Fiberax Networking & Cloud AS29534
Registry name: ITUA-AS IntornTechnic Ltd., UA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29534, 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.
| 193.110.172.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 193.110.173.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 195.140.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.140.244.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.140.245.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.140.246.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS29534: RIPE::AS-FBRX-CLD. 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 (AS29534 isn't in the set, or no route object for AS29534 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 | AS29534 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-FBRX-CLD | RIPE | 10 | 2 | Yes | 2 |
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.
- ROA: origin2
- Route object: none2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 193.110.172.0/24 | ROAs covering it name AS25330, not AS29534. If AS29534 should announce it, add a ROA for AS29534. |
| Route object: none | 193.110.172.0/24 | Route objects for it name AS25330. Add a route object with origin AS29534 in the RIR database for the space. |
| ROA: origin | 193.110.173.0/24 | ROAs covering it name AS25330, not AS29534. If AS29534 should announce it, add a ROA for AS29534. |
| Route object: none | 193.110.173.0/24 | Route objects for it name AS25330. Add a route object with origin AS29534 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29534 whose prefix no peer sees AS29534 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.88.237.0/24 | RIPE | Valid |
| 77.88.238.0/24 | RIPE | Valid |
| 77.88.239.0/24 | RIPE | Valid |
| 195.140.247.0/24 | RIPE | Valid |
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.