# DNS disruption

**URL:** <https://swi-prolog.discourse.group/t/dns-disruption/4980>\
**Category:** SWI-Prolog web site and services\
**Created:** [February 4, 2022, 2:58pm UTC](https://swi-prolog.discourse.group/t/dns-disruption/4980 "2022-02-04T14:58:26Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [February 4, 2022, 2:58pm UTC](https://swi-prolog.discourse.group/t/dns-disruption/4980/1 "2022-02-04T14:58:26Z")

</div>

It seems the ISP DNS services are experiencing problems, making most `*.swi-prolog.org` services inaccessible unless you happen to have the name cached. As the ISP website is also partly inaccessible I assume they know they have a problem …

---

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [February 4, 2022, 3:32pm UTC](https://swi-prolog.discourse.group/t/dns-disruption/4980/2 "2022-02-04T15:32:45Z")

</div>

Is resolved.

---

<div class="post-metadata">

**Author:** ![hasko](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/hasko/32/6185_2.png) [@hasko](https://swi-prolog.discourse.group/u/hasko)\
**Post date:** [March 13, 2024, 8:28pm UTC](https://swi-prolog.discourse.group/t/dns-disruption/4980/3 "2024-03-13T20:28:07Z")

</div>

Seems the problem is back…