bgpreport

Network · data from 2026-11-12

AS207359 TochkaNetwork-AS Tochka Network LLC

Registry name: TochkaNetwork-AS Tochka Network LLC, GE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207359, 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.
179.254.114.0/24 Invalid: origin Other origin only 8 1%low visibility 6
213.182.209.0/24 Invalid: origin Other origin only 2 0%low visibility 2
80.71.228.0/24 No ROA None 671 100% 67
104.238.28.0/24 Valid RIR databaseRIPE 673 100% 66
167.17.45.0/24 Valid RIR databaseRIPE 673 100% 67
169.40.13.0/24 Valid RIR databaseRIPE 673 100% 66
185.127.41.0/24 Valid RIR databaseRIPE 673 100% 67
45.43.148.0/24 Valid RIR databaseRIPE 672 100% 67
87.58.200.0/24 Valid RIR databaseRIPE 672 100% 66
104.239.14.0/24 Valid RIR databaseRIPE 672 100% 66
169.40.12.0/24 Valid RIR databaseRIPE 672 100% 66
185.238.191.0/24 Valid RIR databaseRIPE 672 100% 66
194.58.43.0/24 Valid RIR databaseRIPE 672 100% 66
206.245.146.0/24 Valid RIR databaseRIPE 672 100% 66
213.182.214.0/24 Valid RIR databaseRIPE 672 100% 66
45.43.151.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

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

  • ROA: origin2
  • ROA: none1
  • Route object: none3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin179.254.114.0/24ROAs covering it name AS213823, not AS207359. If AS207359 should announce it, add a ROA for AS207359.8 of 673
Route object: none179.254.114.0/24Route objects for it name AS213823. Add a route object with origin AS207359 in the RIR database for the space.8 of 673
ROA: origin213.182.209.0/24ROAs covering it name AS218897, not AS207359. If AS207359 should announce it, add a ROA for AS207359.2 of 673
Route object: none213.182.209.0/24Route objects for it name AS218897. Add a route object with origin AS207359 in the RIR database for the space.2 of 673
ROA: none80.71.228.0/24No ROA covers it. Add a ROA for AS207359, maxLength 24.671 of 673
Route object: none80.71.228.0/24No route object for it. Add a route object with origin AS207359 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS207359 whose prefix no peer sees AS207359 announce. Many are kept on purpose (backup routes, space announced only in some places).

31.169.122.0/24RIPEValid
83.97.113.0/24RIPEValid
104.222.180.0/24RIPEValid
104.249.21.0/24RIPEValid
206.245.158.0/24RIPEValid

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.