trochu si s tim formátováním pohrajte, ať se v tom dá aspoň nějak orientovat 😔 kdybyste to vložili rovnou do bloku kódu, tak to hned vypadá líp 😐

traceroute z růžový síťě pro porovnání

Tracing route to www.fio.cz [92.38.6.11]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     1 ms     2 ms  62.141.11.88
  3     3 ms     3 ms     3 ms  89.24.28.9
  4     3 ms     2 ms     3 ms  nix.quantcom.cz [91.210.16.9]
  5     3 ms     3 ms     3 ms  cz-prg.p1sit-4hunge0-7-0-7.quantcom.cz [82.119.246.26]
  6     3 ms     3 ms     3 ms  cz-prg-bbr5-be1.quantcom.cz [82.119.246.231]
  7     4 ms     3 ms     4 ms  82.113.32.83
  8     2 ms     2 ms     3 ms  82.113.52.92
  9     3 ms     4 ms     3 ms  www.fio.cz [92.38.6.11]

Trace complete.

Tracing route to my.headspace.com [13.32.121.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  62.141.11.88
  3     3 ms     3 ms     3 ms  89.24.28.9
  4    10 ms    10 ms     *     prag-b4-link.ip.twelve99.net [62.115.32.254]
  5    10 ms     9 ms     9 ms  ffm-bb2-link.ip.twelve99.net [62.115.124.28]
  6    12 ms    11 ms    12 ms  ffm-b14-link.ip.twelve99.net [62.115.132.211]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     9 ms     9 ms    10 ms  15.230.144.48
 14    10 ms     9 ms    10 ms  server-13-32-121-50.fra60.r.cloudfront.net [13.32.121.50]

Trace complete.

Tracing route to headspace.com [3.174.46.31]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     2 ms     2 ms  62.141.11.88
  3     3 ms     3 ms     3 ms  89.24.28.9
  4    11 ms     *        *     prag-b4-link.ip.twelve99.net [62.115.32.254]
  5    10 ms     9 ms     9 ms  ffm-bb2-link.ip.twelve99.net [62.115.124.28]
  6    13 ms    12 ms    14 ms  ffm-b14-link.ip.twelve99.net [62.115.132.211]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     9 ms     9 ms    10 ms  server-3-174-46-31.fra60.r.cloudfront.net [3.174.46.31]

Trace complete.

Tak ale než si tady přeměřovat pindíky a rovnat to do vzhledné tabulky, kde má @sismon chybu a proč má se síti problémy?

no byla s tim práce asi tak ani ne minutu a výsledek je o dost přehlednější 🤨

Sakra, pardon, ja jsem se snazil to pred odeslanim zformatovat, ale nasel jsem jen single line. Ted uz vidim ze je tam tech moznosti vic, ale musim kliknout na ten plus symbol.

Tusite, co je v tech traceroutech spatne? Pripadne ma nekdo napad jak to lepe odebugovat? Mohl bych napsat nejaky jednoduchy skript, ktery bude tyhle zaznamy provadet treba nekolik hodin, ulozi to do tabulky a nad tim pak hledat anomalie - pokud to dava smysl.

Edited November 6, 2025Nov 6 by sismon

no spíš si udělej sám traceroute s wifi a po kabelu, pak můžeš porovnávat rozdíly, jestli třeba přes wifi to nevede nějakou úplně jinou a divnou cestou kvůli zásahu ios 🤔

Dnes jsem si k tomu konecne sednul, ze udelam ten traceroute pres wifi a kabel. Nicmene ted se mi to zacalo vyskytovat i na kabelu (zda se, ze misto treba 5% vadnych requestu pres wifi se ta chyba projevuje jeste mene casto - cca u 2%).

Tzn. situace je nasledujici - na kabelu i na wifi mi u casti requestu dochazi k chybe ERR_CONNECTION_REFUSED. Stava se ti me i manzelce na vsech zarizenich (3 telefony, 2 tablety, 2 pocitace) na nejnovejsich jablecnych systemech (ios 26.1 a v jednom pripade macos 17). Jediny zpusob jak to resit je zacit pouzivat VPN od Cloudflare pomoci aplikace 1.1.1.1

Napsal jsem si jednoduchy skript, ktery provolava jeden z problematickych serveru a loguje vysledky:

...
2025-11-16T16:30:37.140957 DNS ['65.9.95.27', '65.9.95.4', '65.9.95.90', '65.9.95.73']
2025-11-16T16:30:37.160416 TCP 65.9.95.27:443 OK 18.8ms
2025-11-16T16:30:37.180435 TCP 65.9.95.4:443 OK 19.42ms
2025-11-16T16:30:37.203643 TCP 65.9.95.90:443 OK 22.55ms
2025-11-16T16:30:37.223854 TCP 65.9.95.73:443 OK 19.36ms
2025-11-16T16:30:39.257930 DNS ['65.9.95.27', '65.9.95.4', '65.9.95.90', '65.9.95.73']
2025-11-16T16:30:39.275012 TCP 65.9.95.27:443 OK 16.34ms
2025-11-16T16:30:39.296055 TCP 65.9.95.4:443 OK 20.52ms
2025-11-16T16:30:39.318391 TCP 65.9.95.90:443 OK 21.69ms
2025-11-16T16:30:39.337071 TCP 65.9.95.73:443 TCP_ERROR: [Errno 61] Connection refused <----- ZDE
2025-11-16T16:30:41.365159 DNS ['65.9.95.4', '65.9.95.90', '65.9.95.73', '65.9.95.27']
2025-11-16T16:30:41.386542 TCP 65.9.95.4:443 OK 20.39ms
2025-11-16T16:30:41.405284 TCP 65.9.95.90:443 OK 17.62ms
2025-11-16T16:30:41.423964 TCP 65.9.95.73:443 OK 18.05ms
2025-11-16T16:30:41.441224 TCP 65.9.95.27:443 OK 16.17ms
2025-11-16T16:30:43.466583 DNS ['65.9.95.90', '65.9.95.73', '65.9.95.27', '65.9.95.4']
2025-11-16T16:30:43.487120 TCP 65.9.95.90:443 OK 19.81ms
2025-11-16T16:30:43.506430 TCP 65.9.95.73:443 OK 18.62ms
2025-11-16T16:30:43.525993 TCP 65.9.95.27:443 OK 18.89ms
2025-11-16T16:30:43.548085 TCP 65.9.95.4:443 OK 21.2ms
...

Lze z toho neco vycist? Pripadne dava vam smysl volat technika? Jedine dalsi reseni je pak prechod k O2, ktery nabizi pomalejsi DSL internet

To že IP je Amazonu https://www.whois.com/whois/65.9.95.73

Stejne se to chova i u dalsich domen, ktere takto provolavam - napriklad:

• kb.cz

...
025-11-17T17:39:50.916206 DNS ['194.50.226.49', '194.50.202.49']
2025-11-17T17:39:50.939477 TCP 194.50.226.49:443 OK 22.49ms
2025-11-17T17:39:50.963916 TCP 194.50.202.49:443 OK 23.69ms
2025-11-17T17:39:52.993036 DNS ['194.50.202.49', '194.50.226.49']
2025-11-17T17:39:53.017660 TCP 194.50.202.49:443 TCP_ERROR: [Errno 61] Connection refused
2025-11-17T17:39:53.036438 TCP 194.50.226.49:443 TCP_ERROR: [Errno 61] Connection refused
2025-11-17T17:39:55.071103 DNS ['194.50.226.49', '194.50.202.49']
...

• fio.cz

...
2025-11-16T17:33:39.109958 DNS ['92.38.6.11']
2025-11-16T17:33:39.128594 TCP 92.38.6.11:443 TCP_ERROR: [Errno 61] Connection refused
2025-11-16T17:33:41.158608 DNS ['92.38.6.11']
2025-11-16T17:33:41.179849 TCP 92.38.6.11:443 OK 20.37ms
2025-11-16T17:33:43.210113 DNS ['92.38.6.11']
2025-11-16T17:33:43.237606 TCP 92.38.6.11:443 OK 26.65ms
...

• headspace.com

...
2025-11-16T17:16:26.995273 TCP 65.9.95.4:443 OK 20.18ms
2025-11-16T17:16:27.016136 TCP 65.9.95.27:443 OK 20.34ms
2025-11-16T17:16:27.042568 TCP 65.9.95.90:443 OK 25.95ms
2025-11-16T17:16:27.062559 TCP 65.9.95.73:443 TCP_ERROR: [Errno 61] Connection refused
2025-11-16T17:16:29.102739 DNS ['65.9.95.27', '65.9.95.90', '65.9.95.73', '65.9.95.4']
2025-11-16T17:16:29.119924 TCP 65.9.95.27:443 TCP_ERROR: [Errno 61] Connection refused
2025-11-16T17:16:29.141634 TCP 65.9.95.90:443 TCP_ERROR: [Errno 61] Connection refused
...

Dnes jsem se spojil s podporou Vodafone a technika napadlo na routeru zablokovat IPv6 a vynucovat IPv4.

Uz je to hodina a zatim se zda byt vse funkcni

koukám, že ani headspace a ani fio ipv6 nemají, ale i tak by to nějak mělo fungovat 🤔

Tak s odstupem nekolika dnu potvrzuji, ze vse funguje - reseni bylo deaktivovat IPv6 v nastaveni modemu