We are trying to sort out a viable method to archive the
notifications.  I'm not exactly sure (offhand) where this fits
into priorities, but I believe it's sooner than later :)

I'll try to get more details after the weekend.

Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]

On Sat, 25 Jan 2003, Chris Scott wrote:

> Tucows,
>
> Is there any chance of the notifications being archived somewhere?  I apologize if 
>they are but I looked at the discuss list archives and the resellers site and didn't 
>find anything.  I think this has been brought up before but I don't remember if there 
>was a response.
>
> This would make it easier for those of us that don't have access to our email 
>account that receives such notices to be re-informed of outages.
>
> Oh, and the RWI is not the place to archive them ;-)
>
> Thanks,
> Chris Scott
>
> ---------- Original Message ----------------------------------
> From: [EMAIL PROTECTED]
> Date: Sat, 25 Jan 2003 11:42:28 -0800 (PST)
>
> >
> >On Sat, 25 Jan 2003, Domainwizardry.com wrote:
> >> unable to establish socket.....since 10am EST
> >
> >1. OpenSRS Maintenance Window Notification
> >------------------------------------------
> >
> >The LIVE Environment for OpenSRS will be taken offline for NeuStar and
> >Verisign Registry imposed scheduled maintenance windows. Tucows is
> >taking advantage of the Registry outages to perform its own maintenance
> >window. This will ensure minimal impact to your operation.
> >
> >Date: Saturday, January 25 2003 UTC
> >Time: 1400 hrs - 2100 hrs UTC
> >Duration: 7 hours
> >Systems Affected: Production Environment
> >Purpose: Operational and Infrastructure Improvements
> >
> >This will affect all domains orders (including transfers, renewals),
> >as well as the digital certificate system, and new orders for the
> >e-mail service system. Domain owners will not be able to manage
> >their domains, and the WHOIS will not be available.
> >
> >However, customers of the e-mail service system will be able to
> >send and receive their e-mails.
> >
> >
> >
>
>

Reply via email to