sch-einesystem | Blog
| ||
|
|
|
|
|
|
 | |
| [0] |
20250209-1400-0-1.jpg |
 | |
| [1] |
20250209-1400-0-2.jpg |
 | |
| [2] |
20250209-1400-0-3.jpg |
 | |
| [3] |
20250209-1400-0-4.jpg |
| Nachdem ich mich den führne Morgen und Vormittag über mit dem Netzwerkproblem was den Taffic der in Richtung Ostblock geht nagehtgweidemt habe, dort brachen Verbindungen die über einen meiner mehr als 5 Uptreams kommen/gehen sproardsich ab und jetzt kurz vor 14:00 Uhr tut sich etwas. Jener der Upstream Provider bei dem das Problem auftritt hat sich gemeldet.
-------- Nachricht -------- Betreff: We have received your ticket #1516953 -0bcd- Datum: Sun, 09 Feb 2025 03:46:54 +0000 Von: Support <support@***> Antwort an: support@*** An: maximilian.baehring@*** We have received your request and someone will be looking at it shortly. -------- Nachricht -------- Datum: Sun, 09 Feb 2025 04:01:26 +0000 Von: *** <info@***> Antwort an: *** <info@***> An: maximilian.baehring@*** Dear Maximilian Baehring, Thank you for contacting support. Your ticket with ID #664670 has been created. You can track the status of your ticket or add comments by following this link: https://***/tickets/view/664670. < *** > Our support specialists will review your issue within 48 hours. Best regards Your technical support 664670:2810300 -------- Nachricht -------- Betreff: Update to Ticket #1516953 -5afb- Datum: Sun, 09 Feb 2025 12:54:19 +0000 Von: Support <support@***> Antwort an: support@*** An: maximilian.baehring@**** Hi We get the route to **** over DE-CIX, but the peers nexthop is unreachable, thus traffic drops at AS62255. Have re-routed traffic over transit and can reach it now: PING ***(***) 56 data bytes 64 bytes from ***: icmp_seq=1 ttl=57 time=45.5 ms 64 bytes from ***: icmp_seq=2 ttl=57 time=44.9 ms 64 bytes from ***: icmp_seq=3 ttl=57 time=45.5 ms 64 bytes from ***: icmp_seq=4 ttl=57 time=48.0 ms --- *** ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 44.939/46.019/48.052/1.208 ms Best regards, -- To reply to this ticket, update the ticket in our support area at *** < *** >. | |