Send Outages-discussion mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: [outages] Verizon Outage Affecting All US Customers
Roaming Abroad (Frank Bulk)
2. Outage ns1-ns5.he.net, clientHold in WHOIS for he.net
(Michael B. Williams)
3. Re: Outage ns1-ns5.he.net, clientHold in WHOIS for he.net
(Tom Hek)
----------------------------------------------------------------------
Message: 1
Date: Sat, 29 Jun 2024 18:53:15 -0500
From: "Frank Bulk" <[email protected]>
To: <[email protected]>
Subject: Re: [Outages-discussion] [outages] Verizon Outage Affecting
All US Customers Roaming Abroad
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Bell Canada tweeted this: https://x.com/Bell_Support/status/1807073085566202164
Frank
-----Original Message-----
From: Outages <[email protected]> On Behalf Of Bill Woodcock via
Outages
Sent: Saturday, June 29, 2024 4:47 AM
To: [email protected]
Subject: Re: [outages] Verizon Outage Affecting All US Customers Roaming Abroad
I live in Paris, and traveled to Luxembourg and the Netherlands in the last
week? My Free eSIM had solidly consistent data roaming in both LU and NL (and
works fine at home in Paris), but my T-Mobile eSIM has been intermittent,
sometimes working for a while, but then not for hours at a time. I also
normally get an SMS from T-Mobile immediately when I enter a new country, and
that didn?t seem to be happening reliably either.
> On Jun 28, 2024, at 19:30, Wood, Adam via Outages <[email protected]> wrote:
>
> Just had a colleague land in Paris. He?s on AT&T and says it?s much worse
> than being reported. He scrambled to get an E-SIM from a local company just
> for basic options. No bars at all without it.
> From: Outages <[email protected]> On Behalf Of Doug Barrett via
> Outages
> Sent: Friday, June 28, 2024 10:27 AM
> To: Rusty Dekema <[email protected]>
> Cc: [email protected]
> Subject: Re: [outages] Verizon Outage Affecting All US Customers Roaming
> Abroad
> Domestic Verizon phones through our enterprise are now showing SOS only.
> On Fri, Jun 28, 2024 at 4:35?AM Rusty Dekema via Outages
> <[email protected]> wrote:
> For me personally, and others traveling in my vicinity, this outage has been
> resolved.
> It appears that Syniverse was responsible for the outage; they have released
> a statement which, according to my experience, somewhat understates the
> extent of the trouble:
> https://link.edgepilot.com/s/91f92b6e/niw2K1jWnkm5ZYYGEDlL5g?u=https://www.syniverse.com/news-and-events/statement-from-syniverse-regarding-syniverse-addresses-service-disruption-issues-for-overseas-travelers
> Cheers,
> Rusty D.
> Sent from my iPhone
>
>
> On Jun 27, 2024, at 5:13?PM, Martin, James F via Outages
> <[email protected]> wrote:
> ?Just wanted to call this to the attention of the group. According to X, its
> been going on for a while ~24hrs.
> "@VerizonSupport
> 47m
> Replying to
> @ApolloPappas
> We're sorry about the issues you're having with service. There's a current
> outage for all international customers. We're working to resolve this, and
> there's no current ETA. ~Jesse"
> Regards,
> James Martin
> [email protected]
> BUSINESS USE
> _______________________________________________
> Outages mailing list
> [email protected]
> https://link.edgepilot.com/s/4f63ac46/DXedGqyns0SDj6lRw8iJAA?u=https://puck.nether.net/mailman/listinfo/outages
> _______________________________________________
> Outages mailing list
> [email protected]
> https://link.edgepilot.com/s/4f63ac46/DXedGqyns0SDj6lRw8iJAA?u=https://puck.nether.net/mailman/listinfo/outages
> _______________________________________________
> Outages mailing list
> [email protected]
> https://link.edgepilot.com/s/4f63ac46/DXedGqyns0SDj6lRw8iJAA?u=https://puck.nether.net/mailman/listinfo/outages
-Bill
Links contained in this email have been replaced. If you click on a link in the
email above, the link will be analyzed for known threats. If a known threat is
found, you will not be able to proceed to the destination. If suspicious
content is detected, you will see a warning.
------------------------------
Message: 2
Date: Fri, 5 Jul 2024 04:42:32 +1000
From: "Michael B. Williams" <[email protected]>
To: Jay Ashworth <[email protected]>
Cc: Outages Discussion <[email protected]>, Tom Hek
<[email protected]>
Subject: [Outages-discussion] Outage ns1-ns5.he.net, clientHold in
WHOIS for he.net
Message-ID:
<CAGj=18goap3p4rsbewxx6b-xxvdf4toudziwof-_ri21ihk...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Outages discussion
The issue is they can?t even receive email right now so unless they have
their personal email on here they might not know there is an issue. I also
reached out on Twitter?
Sent from Gmail Mobile
On Fri, Jul 5, 2024 at 04:41 Jay Ashworth <[email protected]> wrote:
> Hopefully somebody who actually works at Hurricane Electric will chime in
> fairly promptly, and let us restrain comment on this list to that actual
> thread.
>
> Any further commentary that does not involve an he employee should move
> over to -discuss.
>
>
> On July 4, 2024 2:34:59 PM EDT, "Michael B. Williams via Outages" <
> [email protected]> wrote:
>
>> I?m seeing the same issues.
>>
>> For those who don?t know the clientHold status code tells a domain's
>> registry to not activate a domain in the DNS and as a consequence, it will
>> not resolve. It is an uncommon status that is usually enacted during legal
>> disputes, non-payment, or when a domain is subject to deletion.
>> Given the expiry of this domain is 2033 something else is going on?
>> anyone have a contact at HE who could shead some light on this situation?
>>
>> Sent from Gmail Mobile
>>
>>
>> On Fri, Jul 5, 2024 at 04:28 Tom Hek via Outages <[email protected]>
>> wrote:
>>
>>> Hello Outages,
>>>
>>> Seeing a bunch of resolution failures on our resolvers, after diagnosis
>>> I tracked it down to HE.net being in clientHold:
>>>
>>> Domain Name: HE.NET
>>> Registry Domain ID: 486609_DOMAIN_NET-VRSN
>>> Registrar WHOIS Server: whois.networksolutions.com
>>> Registrar URL: http://networksolutions.com
>>> Updated Date: 2024-07-04T15:06:46Z
>>> Creation Date: 1995-07-31T04:00:00Z
>>> Registry Expiry Date: 2033-07-30T04:00:00Z
>>> Registrar: Network Solutions, LLC
>>> Registrar IANA ID: 2
>>> Registrar Abuse Contact Email: [email protected]
>>> Registrar Abuse Contact Phone: +1.8777228662
>>> Domain Status: clientHold https://icann.org/epp#clientHold
>>> Domain Status: clientTransferProhibited
>>> https://icann.org/epp#clientTransferProhibited
>>> Name Server: NS1.HE.NET
>>> Name Server: NS2.HE.NET
>>> Name Server: NS3.HE.NET
>>> Name Server: NS4.HE.NET
>>> Name Server: NS5.HE.NET
>>> DNSSEC: unsigned
>>> URL of the ICANN Whois Inaccuracy Complaint Form:
>>> https://www.icann.org/wicf/
>>> >>> Last update of whois database: 2024-07-04T18:19:09Z <<<
>>>
>>> ns1-5.he.net stopped resolving due to this as HE.net disappeared from
>>> the .net zone, so all domains that use them as a authoritative DNS might
>>> stop resolving soon as well.
>>>
>>> Kind regards,
>>>
>>> Tom Hek
>>> _______________________________________________
>>> Outages mailing list
>>> [email protected]
>>> https://puck.nether.net/mailman/listinfo/outages
>>>
>> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240705/93c230dd/attachment-0001.htm>
------------------------------
Message: 3
Date: Thu, 04 Jul 2024 20:47:15 +0200
From: "Tom Hek" <[email protected]>
To: "Michael B. Williams" <[email protected]>, "Jay
Ashworth" <[email protected]>
Cc: "Outages Discussion" <[email protected]>
Subject: Re: [Outages-discussion] Outage ns1-ns5.he.net, clientHold in
WHOIS for he.net
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
I tried to reach out to their support via phone, but the person picking up the
phone said everything was working and didn't see a reason to create a ticket
about it, even after trying to explain what the WHOIS status meant and that
their main domain is currently not resolving. Well, I tried. :)
Kind regards,
Tom
On Thu, 4 Jul 2024, at 20:42, Michael B. Williams wrote:
> Outages discussion
>
> The issue is they can?t even receive email right now so unless they have
> their personal email on here they might not know there is an issue. I also
> reached out on Twitter?
>
> Sent from Gmail Mobile
>
>
> On Fri, Jul 5, 2024 at 04:41 Jay Ashworth <[email protected]> wrote:
>> Hopefully somebody who actually works at Hurricane Electric will chime in
>> fairly promptly, and let us restrain comment on this list to that actual
>> thread.
>>
>> Any further commentary that does not involve an he employee should move over
>> to -discuss.
>>
>>
>> On July 4, 2024 2:34:59 PM EDT, "Michael B. Williams via Outages"
>> <[email protected]> wrote:
>>> I?m seeing the same issues.
>>>
>>> For those who don?t know the clientHold status code tells a domain's
>>> registry to not activate a domain in the DNS and as a consequence, it will
>>> not resolve. It is an uncommon status that is usually enacted during legal
>>> disputes, non-payment, or when a domain is subject to deletion.
>>>
>>> Given the expiry of this domain is 2033 something else is going on? anyone
>>> have a contact at HE who could shead some light on this situation?
>>>
>>> Sent from Gmail Mobile
>>>
>>>
>>> On Fri, Jul 5, 2024 at 04:28 Tom Hek via Outages <[email protected]>
>>> wrote:
>>>> __
>>>> Hello Outages,
>>>>
>>>> Seeing a bunch of resolution failures on our resolvers, after diagnosis I
>>>> tracked it down to HE.net being in clientHold:
>>>>
>>>> Domain Name: HE.NET
>>>> Registry Domain ID: 486609_DOMAIN_NET-VRSN
>>>> Registrar WHOIS Server: whois.networksolutions.com
>>>> Registrar URL: http://networksolutions.com
>>>> Updated Date: 2024-07-04T15:06:46Z
>>>> Creation Date: 1995-07-31T04:00:00Z
>>>> Registry Expiry Date: 2033-07-30T04:00:00Z
>>>> Registrar: Network Solutions, LLC
>>>> Registrar IANA ID: 2
>>>> Registrar Abuse Contact Email: [email protected]
>>>> Registrar Abuse Contact Phone: +1.8777228662
>>>> Domain Status: clientHold https://icann.org/epp#clientHold
>>>> Domain Status: clientTransferProhibited
>>>> https://icann.org/epp#clientTransferProhibited
>>>> Name Server: NS1.HE.NET
>>>> Name Server: NS2.HE.NET
>>>> Name Server: NS3.HE.NET
>>>> Name Server: NS4.HE.NET
>>>> Name Server: NS5.HE.NET
>>>> DNSSEC: unsigned
>>>> URL of the ICANN Whois Inaccuracy Complaint Form:
>>>> https://www.icann.org/wicf/
>>>> >>> Last update of whois database: 2024-07-04T18:19:09Z <<<
>>>>
>>>> ns1-5.he.net stopped resolving due to this as HE.net disappeared from the
>>>> .net zone, so all domains that use them as a authoritative DNS might stop
>>>> resolving soon as well.
>>>>
>>>> Kind regards,
>>>>
>>>> Tom Hek
>>>> _______________________________________________
>>>> Outages mailing list
>>>> [email protected]
>>>> https://puck.nether.net/mailman/listinfo/outages
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/outages-discussion/attachments/20240704/90b97600/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 169, Issue 1
**************************************************