<?xml version="1.0" encoding="ISO-8859-1"?>

 <rss version="0.91">

<channel>
<title>ISPStatus</title><link>http://www.ispstatus.org/</link><description>ISPStatus</description><language>en-gb</language><item>
<title>DreamHost - luanda filesystem check fun!</title>
<link>http://www.ispstatus.org/readmore/13301/</link>
<description><p>luanda was rebooted earlier this today and the fielsystem came back read-only. So, unmounted and did a regular filesystem check and all was happy, till we rebooted and the filesystem started throwing up erros again. So now we&#8217;re a thorough filesystem check to sort this whole mess out. All the user data is intact so no need to worry there (and of course, there is the nightly backups too). </p>
<p>This filesystem check will likely take a few hours to complete and is dependent on a number of factors that&#8217;ll determine how long the filesystem check will run. PETA has been going after us after word leaked out that we were using entrails to determine fsck times for these posts, so we can&#8217;t be any more accurate or inaccurate than that for an ETA.  </p>
<p>This affects less that 1% of our shared web hosting customers, so please check your web panel to figure out what server your on. For any other servers, please create a support ticket.</p>
</description>
</item>
<item>
<title>Ebay - Scheduled Maintenance For This Week</title>
<link>http://www.ispstatus.org/readmore/13299/</link>
<description>The eBay system will be undergoing general maintenance from approximately 23:00 PT (11pm) on Thursday, September 9th to 01:00 PT (1am) on Friday, September 10th. During this maintenance period, certai...</description>
</item>
<item>
<title>Zen - #1940 Routing & Core Network - New BTW Ethernet London Bearers   (Update)</title>
<link>http://www.ispstatus.org/readmore/13295/</link>
<description><p></p><p>Start: Fri, 10th Sep 2010 13:00<br>End: Fri, 10th Sep 2010 14:30<br>Update: Fri, 10th Sep 2010 14:30<br>Edited: Wed, 8th Sep 2010 15:08<br>Status: Up<br>Maintenance: Planned</p></description>
</item>
<item>
<title>Zen - #1941 Voice - Continued issues with inbound voip (New)</title>
<link>http://www.ispstatus.org/readmore/13296/</link>
<description><p>The problems detected yesterday affecting customers who have VOIP from ourselves have returned. This problem would only affect larger customers who would have a lot of users on inbound calls only.<br><br>This issue comes from a problem with one of our third party suppliers and we are currently working with them for a resolution.<br><br>Further updates will be posted here when available.<br><br>Zen regret any inconvenience this may cause.<br></p><p>Start: Wed, 8th Sep 2010 14:43<br>Update: Wed, 8th Sep 2010 16:45<br>Edited: Wed, 8th Sep 2010 14:44<br>Status: Partial<br>Maintenance: Emergency</p></description>
</item>
<item>
<title>Zen - #1940 Routing & Core Network - New BTW Ethernet London Bearers   (New)</title>
<link>http://www.ispstatus.org/readmore/13297/</link>
<description><p>Maintenance work is being performed on our London Metro ring used to service DSL customers on the BT 21CN platform. <br><br>No disruption to service is expected, this service alert is being raised as a precautionary measure.</p><p>Start: Fri, 10th Sep 2010 13:00<br>End: Fri, 10th Sep 2010 14:30<br>Update: Wed, 8th Sep 2010 14:30<br>Edited: Wed, 8th Sep 2010 14:40<br>Status: Up<br>Maintenance: Planned</p></description>
</item>
<item>
<title>Zen - #1939 Shared Linux Hosting - rscp01.hosting.zen.net.uk server maintenance. (New)</title>
<link>http://www.ispstatus.org/readmore/13293/</link>
<description><p>Our engineers have identified a potential service impacting issue on the server and as such we need to perform emergency maintenance. <br><br>The server will be taken off-line for a short period whilst software patches are applied to the server. <br><br>Customer will loose access to all services on the server 5-10 minutes whilst it is restarted. <br><br>Zen regret any inconvenience this may cause.</p><p>Start: Thu, 9th Sep 2010 00:01<br>End: Thu, 9th Sep 2010 01:00<br>Update: Thu, 9th Sep 2010 01:00<br>Edited: Wed, 8th Sep 2010 14:07<br>Status: Outage<br>Maintenance: Emergency</p></description>
</item>
<item>
<title>madasafish - Access to Care4Free websites and email (63356) - RESOLVED</title>
<link>http://www.ispstatus.org/readmore/13294/</link>
<description>This is an update to yesterday's post regarding Care4Free customers' access to our email and web servers.

Our domain registrar has resolved the underlying problem and DNS appears to have fully propagated. As such, access to email and websites has been restored for all customers.

Please accept our sincere apologies for any inconvenience caused by this problem.

Regards,

Ben Trimble
Customer Support</description>
</item>
<item>
<title>madasafish - Inbound Email Delays (63388) - RESOLVED</title>
<link>http://www.ispstatus.org/readmore/13292/</link>
<description>This is an update to this morning's post about delays that may have affected the arrival of incoming email.

The underlying problem has been resolved and the mail queues have returned to normal levels. No email has been lost and all messages should now be arriving in a timely fashion.

Kind Regards,

Bob Pullen
Customer Support</description>
</item>
<item>
<title>madasafish - Inbound Email Delays (63388) - NEW</title>
<link>http://www.ispstatus.org/readmore/13290/</link>
<description>Our monitoring systems have identified a rise in the volume of messages queued on our inbound mail platform.

This could result in delays in affecting the arrival of customers' email to their mailboxes.

Our engineers are investigating and we'll provide another update once further information is made available.

Apologies for the inconvenience.

Kind regards,

Bob Pullen
Customer Support</description>
</item>
<item>
<title>Zen - #1930 Broadband (xDSL) - Problems on Basildon exchange (Close)</title>
<link>http://www.ispstatus.org/readmore/13288/</link>
<description><p>BT have completed works overnight to restore connections to the remaining customers affected. Any customers continuing to have problems please contact Technical support for further assistance.<br><br>Zen regret any inconvenience this may cause.</p><p>Start: Fri, 3rd Sep 2010 11:28<br>Clear: Wed, 8th Sep 2010 09:04<br>Edited: Wed, 8th Sep 2010 09:04<br>Status: Up<br>Maintenance: None</p></description>
</item>
<item>
<title>Jumba - Scheduled: SYD1: Network Maintenance [postponed]</title>
<link>http://www.ispstatus.org/readmore/13287/</link>
<description>Advisory #3387 has been updated. The details are below. <br />
<br />
Status: Scheduled, Low Impact, Postponed <br />
Start: - <br />
<br /><strong>Update at Tue, Aug 24 2010 11:52 am</strong><br /><br />During this time we will be performing maintenance on our Sydney network.<br />
<br />
This maintenance window will have the following impacts:<br />
- PIPE Sydney connectivity will be interrupted for up to 1 hour. <br />
- Vocus Sydney connectivity will be interrupted for up to 1 hour.<br />
<br />
There may be a brief period of packet loss while traffic flowing through the affected links automatically reroutes. No further impact is expected.<br />
<br />
This maintenance window also involves bringing on additional upstream carrier circuits however no customer impact is expected when this change is made.<br /><br /> ------<br /><br /><strong>Update at Thu, Sep 02 2010 10:15 pm</strong><br /><br />This maintenance has been postponed. A revised ETA will be posted shortly.<br /><br /> ------<br /></description>
</item>
<item>
<title>Jumba - Scheduled: Updates to vCenter / vSphere service (CBR) [current]</title>
<link>http://www.ispstatus.org/readmore/13286/</link>
<description>Advisory #3399 has been updated. The details are below. <br />
<br />
Status: Scheduled, Low Impact, Current <br />
Start: 08/09/2010 11:00 <br />
ETA: 08/09/2010 18:00 <br />
<br /><strong>Update at Sat, Aug 28 2010 07:39 pm</strong><br /><br />Customers are advised that due to upgrades on our VMware virtual infrastructure in Canberra, access to vSphere will be limited during this window.<br />
At the completion of the upgrades, customers are advised that the access point for vCenter will change from vc.vde.net.au to the new address of vcenter1.cbr1.aussiehq.net.au.<br />
<br />
Additionally, customers using the vSphere client to access their VM's will need to upgrade their client to the newer 4.1 version. <br />
This can be obtained from our mirror:<br />
http://vmware.mirror.aussiehq.net.au/VMware-viclient.exe<br />
<br />
If VM actions are required during this time, customers are advised to contact the service desk.<br />
<br />
We apologise in advance for the inconvenience caused.<br />
<br /><br /> ------<br /><br /><strong>Update at Wed, Sep 08 2010 11:33 am</strong><br /><br />The updates are now in progress.<br /><br /> ------<br /></description>
</item>
<item>
<title>Jumba - Scheduled: SYD1: Network Maintenance [postponed]</title>
<link>http://www.ispstatus.org/readmore/13285/</link>
<description>Advisory #3387 has been updated. The details are below. <br />
<br />
Status: Scheduled, Low Impact, Postponed <br />
Start: - <br />
<br /><strong>Update at Tue, Aug 24 2010 11:52 am</strong><br /><br />During this time we will be performing maintenance on our Sydney network.<br />
<br />
This maintenance window will have the following impacts:<br />
- PIPE Sydney connectivity will be interrupted for up to 1 hour. <br />
- Vocus Sydney connectivity will be interrupted for up to 1 hour.<br />
<br />
There may be a brief period of packet loss while traffic flowing through the affected links automatically reroutes. No further impact is expected.<br />
<br />
This maintenance window also involves bringing on additional upstream carrier circuits however no customer impact is expected when this change is made.<br /><br /> ------<br /><br /><strong>Update at Thu, Sep 02 2010 10:15 pm</strong><br /><br />This maintenance has been postponed. A revised ETA will be posted shortly.<br /><br /> ------<br /></description>
</item>
<item>
<title>Jumba - Scheduled: Updates to vCenter / vSphere service (CBR) [current]</title>
<link>http://www.ispstatus.org/readmore/13284/</link>
<description>Advisory #3399 has been updated. The details are below. <br />
<br />
Status: Scheduled, Low Impact, Current <br />
Start: 08/09/2010 11:00 <br />
ETA: 08/09/2010 13:00 <br />
<br /><strong>Update at Sat, Aug 28 2010 07:39 pm</strong><br /><br />Customers are advised that due to upgrades on our VMware virtual infrastructure in Canberra, access to vSphere will be limited during this window.<br />
At the completion of the upgrades, customers are advised that the access point for vCenter will change from vc.vde.net.au to the new address of vcenter1.cbr1.aussiehq.net.au.<br />
<br />
Additionally, customers using the vSphere client to access their VM's will need to upgrade their client to the newer 4.1 version. <br />
This can be obtained from our mirror:<br />
http://vmware.mirror.aussiehq.net.au/VMware-viclient.exe<br />
<br />
If VM actions are required during this time, customers are advised to contact the service desk.<br />
<br />
We apologise in advance for the inconvenience caused.<br />
<br /><br /> ------<br /><br /><strong>Update at Wed, Sep 08 2010 11:33 am</strong><br /><br />The updates are now in progress.<br /><br /> ------<br /></description>
</item>
<item>
<title>Linode - RESOLVED - Packet loss affecting some Linodes in Fremont</title>
<link>http://www.ispstatus.org/readmore/13283/</link>
<description>
<div xmlns="http://www.w3.org/1999/xhtml"><p style="padding-left: 10%; text-indent: -10%;"><strong >10:06am (EDT): </strong>Connectivity has returned to normal and we'll continue to monitor at this time.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >10:00am (EDT): </strong>We are looking into packet loss affecting some Linodes in the Fremont facility.  There is no reason to issue reboots as Linodes are still running.</p></div>
</description>
</item>
<item>
<title>Linode - RESOLVED - Connectivity issues affecting some Linodes in Newark</title>
<link>http://www.ispstatus.org/readmore/13282/</link>
<description>
<div xmlns="http://www.w3.org/1999/xhtml"><p style="padding-left: 10%; text-indent: -10%;"><strong >8:06am (EDT): </strong>Reports indicate that connectivity has returned to normal.  We will keep monitoring at this time.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >5:13am (EDT): </strong>We have received reports of intermittent connectivity to our Newark facility.  While our network appears healthy, we are working with the NOC to determine if this is an issue upstream from us.</p></div>
</description>
</item>
<item>
<title>Linode - COMPLETED - Scheduled Network Maintenance in Newark: August 8, 2010</title>
<link>http://www.ispstatus.org/readmore/13281/</link>
<description>
<div xmlns="http://www.w3.org/1999/xhtml"><p style="font-weight: bold">Saturday, August 8th, 2010</p>
<p style="padding-left: 10%; text-indent: -10%;"><strong>8:20pm (EDT): </strong>Maintenance completed.  This concludes a major upgrade to our Newark facility's network.  Enjoy!</p>
<p style="padding-left: 10%; text-indent: -10%;"><strong>8:00pm (EDT): </strong>Maintenance commencing.</p>

<br>
<p style="font-weight: bold">Wednesday, August 4th, 2010</p>
<p style="padding-left: 10%; text-indent: -10%;"><strong>4:45pm (EDT): </strong>The Newark facility will undergo network maintenance between 8:00pm and 10:00pm EDT, August 8th.  We do not expect any downtime during this maintenance window.</p></div>
</description>
</item>
<item>
<title>Linode - RESOLVED - Network issues in Dallas, Fremont, Atlanta, and Newark</title>
<link>http://www.ispstatus.org/readmore/13280/</link>
<description>
<div xmlns="http://www.w3.org/1999/xhtml"><p style="padding-left: 10%; text-indent: -10%;"><strong >8:59am (EDT): </strong>The attack against Atlanta has been mitigated and connectivity has returned to normal.  We will continue to monitor all four locations at this time.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >8:49am (EDT): </strong>The attack against Fremont has been mitigated and connectivity has returned to normal.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >8:40am (EDT): </strong>The attacks against both Dallas and Newark have been mitigated and connectivity has returned to normal.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >8:38am (EDT): </strong>This appears to be a malicious DDoS attack against all four Linode facilities.  We are currently working on mitigating them.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >8:25am (EDT): </strong>We are looking into packet loss affecting some Linodes in all four facilities.  There is no reason to issue reboots as Linodes are still running.</p></div>
</description>
</item>
<item>
<title>Linode - Packet Loss affecting some Linodes in London</title>
<link>http://www.ispstatus.org/readmore/13279/</link>
<description>
<div xmlns="http://www.w3.org/1999/xhtml"><p style="padding-left: 10%; text-indent: -10%;"><strong >1:46pm (EDT): </strong>Connectivity has returned to normal and we will continue to monitor at this time.</p>

<p style="padding-left: 10%; text-indent: -10%;"><strong >1:41pm (EDT): </strong>We are looking into a network issue in the London facility.  There is no reason to issue reboots as Linodes are still up at this time.</p></div>
</description>
</item>
<item>
<title>Second Life - Emerald Viewer to be Blocked From Second Life</title>
<link>http://www.ispstatus.org/readmore/13278/</link>
<description><!-- [DocumentBodyStart:c491471b-e4e9-4483-9d1d-07d8df6fbdfd] --><div class='jive-rendered-content'><p>As of 10am PT Wednesday, September 8, the Emerald Viewer will be blocked from logging in to Second Life as a result of violations of our <a class="jive-link-external-small" href="http://secondlife.com/corporate/tpv.php">Policy on Third Party Viewers</a>. Residents who have been using any version of the Emerald Viewer will need to use a different Viewer to access Second Life. You can download the official Second Life Viewer, developed by Linden Lab, <a class="jive-link-external-small" href="http://secondlife.com/support/downloads/">here</a>. Or you can learn more about alternative Viewers, developed by third parties, <a class="jive-link-external-small" href="http://viewerdirectory.secondlife.com/">here</a>. There are several new Viewers listed in the TPV Directory, so there are many alternatives available to you.</p><p>We take Residents&rsquo; privacy, safety, and security very seriously and will take action to enforce the policies that help protect it. As our CEO, Philip Rosedale, has <a class="jive-link-blog-small" href="http://blogs.secondlife.com/community/features/blog/2010/08/24/malicious-viewers-and-our-third-party-viewer-policy">blogged about</a>, we recently removed the Emerald Viewer from our Third-Party Viewer Directory due to violations of our Policy on Third-Party Viewers.</p><p>Since then, we have been in communication with the Emerald development team and have requested several changes in order to remedy violations of our policy, including changes necessary to meet our privacy requirements, and to address GPL license violations. Unfortunately, the team was unable to comply within a stipulated time frame. As a result, we have decided to block logins from the Emerald Viewer in order to protect our Residents. All versions of the Emerald Viewer will be blocked from logging in to Second Life as of tomorrow at 10am. Please be aware that attempting to circumvent our blocking to access Second Life with a banned Viewer is a violation of the Policy on Third-Party Viewers and may result in the loss of one's account.</p></div><!-- [DocumentBodyEnd:c491471b-e4e9-4483-9d1d-07d8df6fbdfd] --><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/SecondLife?a=lu3PoIEhdqc:d2OOgQeD5ic:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/SecondLife?d=yIl2AUoC8zA" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/SecondLife/~4/lu3PoIEhdqc" height="1" width="1"/></description>
</item>
<item>
<title>DreamHost - Stringray unresponsive</title>
<link>http://www.ispstatus.org/readmore/13277/</link>
<description><p>We&#8217;ve dispatched one of our admins to the physical location of the server to work on getting it back up and we&#8217;ll update this post as soon as we have a handle on the situation and service is restored.</p>
</description>
</item>
<item>
<title>madasafish - Planned Telephony System Maintenance - Tuesday 7th September 5.30pm-Wednesday 8th September 6.00am</title>
<link>http://www.ispstatus.org/readmore/13273/</link>
<description>When's this work happening?
This evening, 7th September into tomorrow morning.

What does it affect?
The telephone system used by our Customer Support Centre.

How long will it take?
Up to ten hours.

What does the work involve?
We are migrating our internal telephony platform across to a new system with improved functionality.

Am I likely to notice the work?
It's unlikely. Some of our support numbers will not work for a brief period of time during the maintenance window, however this part of the work has been scheduled for the early hours of the morning to minimise disruption.

Is there anything else I need to know?
We originally attempted this work last month but encountered some unforeseen problems that meant we had to roll back the changes.

Kind Regards,

Bob Pullen
Customer Support</description>
</item>
<item>
<title>AAISP BT Incident and Planned - Broadband Incident Report : ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE : Reference 24310 : Issue 3 :</title>
<link>http://www.ispstatus.org/readmore/13271/</link>
<description><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***</span></b><br>--------------------------------------------------------------</span></font></p>                          <TABLE  border="0" bgcolor="#ffffff">                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" class="title3" colspan="5" align="middle"><font color="#339966">BT Wholesale - Broadband Incident Report</font></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title" colspan="5"><i>Please read the following incident  report as it could have an impact on some of your end users</i></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title3" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">BT Incident Reference:</TD>                               <TD class="details" width="80">24310</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Issue :</TD>                               <TD align="left" class="details" width="60">3 </TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                                     <TD width="5">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Date:</TD>                                     <TD class="details" width="80">29/08/2010</TD>                                     <TD width="40">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Time:</TD>                                     <TD align="left" class="details" width="60">11:01</TD>                                     <TD width="5">&nbsp;</TD>                                  </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Headline: </TD>                               <TD  colspan="4" class="details" width="340">ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Details: </TD>                               <TD  colspan="4" class="details" width="340">At the moment some of your Broadband End Users will be experiencing a degradation of Broadband Service.</TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Progress Details: </TD>                               <TD  colspan="4" class="details" width="340">BT is making progress towards full restoration of Service. <br>Latest Update:  <br>An Engineer has been tasked to site. <br> Further updates will be provided as soon as possible. <br> <br></TD>                               <TD width="5">&nbsp;</TD>                             </TR>                             <TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Dialling Codes Affected:</TD>                               <TD  colspan="4" class="details" width="340">                                  <TABLE border=0>                                     <TR><TD class="details">01736</TD></TR>                                  </TABLE>                               </TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                     </TABLE><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***<br></b>System Time Stamp: 29/08/2010 10:04</span></span></font></p>                    <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8642345324272940533-5538711000300864770?l=aaisp-btmso.blogspot.com' alt='' /></div></description>
</item>
<item>
<title>AAISP BT Incident and Planned - Broadband Incident Report : ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE : Reference 24310 : Issue 4 :</title>
<link>http://www.ispstatus.org/readmore/13270/</link>
<description><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***</span></b><br>--------------------------------------------------------------</span></font></p>                          <TABLE  border="0" bgcolor="#ffffff">                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" class="title3" colspan="5" align="middle"><font color="#339966">BT Wholesale - Broadband Incident Report</font></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title" colspan="5"><i>Please read the following incident  report as it could have an impact on some of your end users</i></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title3" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">BT Incident Reference:</TD>                               <TD class="details" width="80">24310</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Issue :</TD>                               <TD align="left" class="details" width="60">4 </TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                                     <TD width="5">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Date:</TD>                                     <TD class="details" width="80">29/08/2010</TD>                                     <TD width="40">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Time:</TD>                                     <TD align="left" class="details" width="60">13:30</TD>                                     <TD width="5">&nbsp;</TD>                                  </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Headline: </TD>                               <TD  colspan="4" class="details" width="340">ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Details: </TD>                               <TD  colspan="4" class="details" width="340">At the moment some of your Broadband End Users will be experiencing a degradation of Broadband Service.</TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Progress Details: </TD>                               <TD  colspan="4" class="details" width="340">BT is making progress towards full restoration of Service. <br>Latest Update:  <br>An Engineer has been tasked to site. <br>Further updates will be provided as soon as possible. <br> <br></TD>                               <TD width="5">&nbsp;</TD>                             </TR>                             <TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Dialling Codes Affected:</TD>                               <TD  colspan="4" class="details" width="340">                                  <TABLE border=0>                                     <TR><TD class="details">01736</TD></TR>                                  </TABLE>                               </TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                     </TABLE><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***<br></b>System Time Stamp: 29/08/2010 10:19</span></span></font></p>                    <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8642345324272940533-7918613097388155278?l=aaisp-btmso.blogspot.com' alt='' /></div></description>
</item>
<item>
<title>AAISP BT Incident and Planned - Broadband Incident Report : ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE : Reference 24310 : Issue 5 :</title>
<link>http://www.ispstatus.org/readmore/13269/</link>
<description><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***</span></b><br>--------------------------------------------------------------</span></font></p>                          <TABLE  border="0" bgcolor="#ffffff">                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" class="title3" colspan="5" align="middle"><font color="#339966">BT Wholesale - Broadband Incident Report</font></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title" colspan="5"><i>Please read the following incident  report as it could have an impact on some of your end users</i></TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" class="title3" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">BT Incident Reference:</TD>                               <TD class="details" width="80">24310</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Issue :</TD>                               <TD align="left" class="details" width="60">5 </TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Detected Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Date:</TD>                               <TD class="details" width="80">29/08/2010</TD>                               <TD width="40">&nbsp;</TD>                               <TD align="right" class="details" width="160">Start Time:</TD>                               <TD align="left" class="details" width="60">09:16</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                                     <TD width="5">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Date:</TD>                                     <TD class="details" width="80">29/08/2010</TD>                                     <TD width="40">&nbsp;</TD>                                     <TD align="right" class="details" width="160">Anticipated Clear Time:</TD>                                     <TD align="left" class="details" width="60">15:00</TD>                                     <TD width="5">&nbsp;</TD>                                  </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Headline: </TD>                               <TD  colspan="4" class="details" width="340">ST BURYAN DSL 001 : DEGRADED LOSS OF SERVICE</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                            <TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                            </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Incident Details: </TD>                               <TD  colspan="4" class="details" width="340">At the moment some of your Broadband End Users will be experiencing a degradation of Broadband Service.</TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Progress Details: </TD>                               <TD  colspan="4" class="details" width="340">BT is making progress towards full restoration of Service. <br>Latest Update:  <br>An Engineer is now on site. <br>Further updates will be provided as soon as possible. <br> <br></TD>                               <TD width="5">&nbsp;</TD>                             </TR>                             <TR>                               <TD width="5">&nbsp;</TD>                               <TD  valign="top" class="details" width="160">Dialling Codes Affected:</TD>                               <TD  colspan="4" class="details" width="340">                                  <TABLE border=0>                                     <TR><TD class="details">01736</TD></TR>                                  </TABLE>                               </TD>                               <TD width="5">&nbsp;</TD>                             </TR><TR>                               <TD width="5">&nbsp;</TD>                               <TD width="500" align="middle" colspan="5">&nbsp;</TD>                               <TD width="5">&nbsp;</TD>                             </TR>                     </TABLE><p class=MsoNormal><font size=1 color=black face=Verdana><span style="font-size:8.0pt;font-family:Verdana;color:black">--------------------------------------------------------------<br>Incident Manager - Automatic Mailer.<br><b><span style="font-weight:bold">*** PLEASE DO NOT REPLY TO THIS E-MAIL ***<br></b>System Time Stamp: 29/08/2010 13:21</span></span></font></p>                    <div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8642345324272940533-8597896126518792804?l=aaisp-btmso.blogspot.com' alt='' /></div></description>
</item>
</channel>
</rss>
