bgpreport

Network · data from 2026-11-12

AS35614 Therecom

Registry name: therecomltd Therecom Ltd, UA · PeeringDB

13IPv4 routes 100.0% RPKI valid · 92.3% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS35614, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35614, 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.
31.128.168.0/23 Valid None 673 100% 67
31.128.168.0/24 Valid RIR databaseRIPE 673 100% 66
89.19.113.0/24 Valid RIR databaseRIPE 673 100% 67
94.124.166.0/24 Valid RIR databaseRIPE 673 100% 67
193.105.7.0/24 Valid RIR databaseRIPE 673 100% 66
31.128.170.0/23 Valid RIR databaseRIPE 671 100% 68
89.19.97.0/24 Valid RIR databaseRIPE 671 100% 68
89.19.98.0/24 Valid RIR databaseRIPE 671 100% 68
89.19.99.0/24 Valid RIR databaseRIPE 671 100% 68
89.19.112.0/24 Valid RIR databaseRIPE 671 100% 68
89.19.115.0/24 Valid RIR databaseRIPE 671 100% 68
89.19.116.0/24 Valid RIR databaseRIPE 671 100% 68
2a0c:29c0::/32 Valid RIR databaseRIPE 635 100% 69
31.128.170.0/24 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS35614: AS35614:AS-TH. 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 (AS35614 isn't in the set, or no route object for AS35614 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.

NameDatabaseASNsSets Route objectsAS35614 in itNot covered
AS35614:AS-TH In no IRR database read today.

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 2 are in fix.csv.

  • Route object: none1
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none31.128.168.0/23No route object for it. Add a route object with origin AS35614 in the RIR database for the space.673 of 673
AS-SET: not foundAS35614:AS-THPeeringDB names AS35614:AS-TH; no IRR database read has it.

Route objects not announced

Every route object with origin AS35614 is announced.

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.