Oct 11, 2017 | Information, Outages, Unplanned downtime, Update
UPDATE:
We have seen the services starting to recover and our normal traffic profile is virtually back to normal. Any subscribers still to reconnect may require a router reboot if the issue persists.
The fault is still open with our supplier until the overall service has been restored. Our apologies again to those affected.
+++++++++++++++++++
One of our back-haul providers is aware of an ongoing issue affecting a small section of our lines which is causing either packet loss or intermittent connectivity or sometimes both. NOTE: This isn’t affecting all lines but the following STD codes are those seeing issues through this supplier. We expect an update by 14.30. In the meantime, we apologise if your line is one of those affected.
01171 01173 01179 01200 01214 01282 01372 01483 01485 01512 01513 01514 01515 01517 01518 01519 01527 01553 01604 01628 01905 01932 02010 02011 02030 02031 02032 02033 02034 02035 02070 02071 02072 02073 02074 02075 02076 02077 02078 02079 02080 02081 02082 02083 02084 02085 02086 02087 02088 02089 02311 02380
Sep 17, 2017 | Information, Outages, Unplanned downtime, Update
10:23am UPDATE: the supplier reports that the problem has been resolved and we believe that all circuits are now back online. Affected circuits may need to reboot their router to bring their session back on stream.
The following exchanges are affected by this issue since 6.21am this morning.
BT and the supplier engineers are en-route to work on-site. No time to fix yet but we will update here as we hear more.
Exchanges affected include Barrow, Buntingford, Bottisham, Burwell, Cambridge, Crafts Hill, Cheveley, Clare, Comberton, Costessey, Cherry Hinton, Cottenham, Dereham, Downham Market, Derdingham, Ely, Fakenham, Fordham Cambs, Feltwell, Fulbourn, Great Chesterford, Girton,Haddenham, Histon, Holt, Halstead, Harston, Kentford, Kings Lynn, Lakenheath, Littleport, Madingley, Melbourne, Mattishall, Norwich North, Rorston, Science Park, Swaffham, Steeple Mordon, Soham, Sawston, Sutton, South Wootton, Swavesey, Teversham, Thaxted, Cambridge Trunk, Trumpington, Terrington St Clements, Tittleshall, Willingham, Waterbeach, Watlington, Watton, Buckden, Crowland, Doddington, Eye, Friday Bridge, Glinton, Huntingdon, Long Sutton, Moulton Chapel, Newton Wisbech, Parson Drove, Papworth St Agnes, Ramsey Hunts, Sawtry, Somersham, St Ives, St Neots, Sutton Bridge, Upwell, Warboys, Werrington, Whittlesey, Woolley, Westwood, Yaxley, Ashwell, Gamlingay and Potton
We are aware some other exchanges may be impacted
Update – we have just started to see some circuits recover but have no update from the carrier as yet
Aug 21, 2017 | Information, Planned Work
One of our carriers is performing some planned works on their interconnect in Telehouse North. We have resilient interconnects in other locations, however during the work you may see your connections drop and re-connect over our alternative interconnect.
The work is scheduled for between 29/8/2017 22:00 and 30/8/2017 06:00.
Most circuits will automatically re-conect but a few may require a re-boot or 30-minute power down. If there are any issues please contact support via the normal routes
Jun 23, 2017 | Information, Outages
We are aware that our post.merula.net server was slow / unresponsive between approx 5pm and 8:30pm this evening.
This was due to a customer sending a significant volume of SPAM through the server. We have blocked the affected customer and cleared the Mail Queue on this mail server. Service is now restored.
NOTE that there is a small chance of some outgoing emails being lost while the queue was being cleared – although we believe all legitimate emails have been sent OK.
IF you have sent an email during this time via post.merula.net and have not received a reply you may which to re-send it to ensure it has arrived
We apologies for any issues caused here
Jun 13, 2017 | Information, Outages, Unplanned downtime, Update
RFO 09:40am:
To fix an issue with transient IPv6 and other intermittent routing issues we had seen recently, we were obliged to upgrade the software on one of our core routers. This holds live and backup routes that allow a smooth failover in the case of a single router failing in London. However it now (in an undocumented change from the software supplier) appears with the latest software that the routers set themselves as live on both primary and backup routers – resulting in a routing loop for some IP addresses which had static IP routes originating from this one affected router thus not correctly falling over as previously was the case.
Again, please accept our apologies for this short outage. It shouldn’t have happened.
We are aware of the cause, the problem has now been fixed on this, the one affected router and we have also made sure that all others in the network have been checked and we are confident all are now running properly.
UPDATE 09:27am:
We are aware of the root cause — located at a core switch in our London locations — and are working on bringing this back into service. No ETA yet but we expect this to be resolved shortly. Apologies for the downtime some of you are experiencing.
09:09am We are aware of reports of leased lines down and are investigating. More updates here as we know the cause & ETA to fix.
Jun 7, 2017 | Information, Planned Work
The works detailed below should have no effect on services delivered via the Merula network apart from a possible brief period of routing instability as they re-converge after the link comes back on-line
Service Affected:
Level3 Transit Bearer Manchester
Start of maintenance:
15/06/2017 22:00 BST
End of maintenance:
16/06/2017 03:00 BST
Duration of work:
up to 45 minutes within the outage window
Impact of work:
Outage to listed service
Classification of works:
Standard
Description of works:
Third Party maintenance on underlying fibre connections
