Need help or advice?
Call us FREE 0800 298 2375

Information

INFO: fibre ring maintenance 7th April

 

This work will upgrade the capacity on one leg of our dark-fibre ring. Whilst it won’t cause any outages, we are at elevated risk during the maintenance window and there may be brief transient routing issues when the fibre is brought back on-stream.

Maintenance Window: 21:00 – 07:00 GMT

Primary Date: 07-Apr 2017

2nd Primary Date: 08-Apr 2017

3rd Primary Date: 09-Apr 2017

Location of Maintenance: London

Reason for Maintenance: supplier will perform fiber maintenance to add capacity

INFO: core router maintenance

We are seeing BGP issues affecting one of our core routers in HEX, London. This may involve the need to reboot this equipment late this evening. This will affect a few of our leased line customers only.

INFO: supplier equipment upgrades 23/24 Feb

We don’t expect this to materially affect any of our services but there may be a few instances of slight packet loss or routing transit issues during this window.

Start: 2017-02-23 00:00:00 GMT (UTC + 0)
End: 2017-02-23 04:00:00 GMT (UTC + 0)

LAN(s) AFFECTED
London Juniper

INTRODUCTION
This maintenance is scheduled for the 2nd stage of Juniper software and Routing Engine upgrades.
During this maintenance we will replace both 32 bit RE-S-2000 Routing Engines in Edge1,
Edge2 and Edge3 THN (Telehouse North) with 64 bit RE-S-1800×4 Routing Engines. We will also upgrade the Junos version to 15.1F6-S3 from 13.3R5-S4.1.
All members connected to edge1-thn, edge2-thn and edge3-thn shall experience downtime of up to 20 minutes whilst the RE’s are swapped and rebooted.

INFO: Netgear router vulnerabilities

The following routers are vulnerable as below. New firmware has been released for some of the models and is available from here: http://kb.netgear.com/000036386/CVE-2016-582384

Vulnerability Note VU#582384

Netgear R7000, firmware version 1.0.7.2_1.1.93 and possibly earlier, R6400, firmware version 1.0.1.12_1.0.11 and possibly earlier, and R8000, firmware version 1.0.3.4_1.1.2 and possibly earlier, contain an arbitrary command injection vulnerability.

By convincing a user to visit a specially crafted web site, a remote, unauthenticated attacker may execute arbitrary commands with root privileges on affected routers. An unauthenticated, LAN-based attacker may do the same by issuing a direct request, e.g. by visiting:

http:///cgi-bin/;COMMAND

An exploit demonstrating these vulnerabilities has been publicly disclosed.

Netgear’s advisory confirms that the R6200, R6400, R6700, R7000, R7100LG, R7300, R7900, and R8000 are vulnerable, though affected firmware versions are not enumerated. The vendor has indicated that their advisory will be updated as firmware updates are released.

Possible LNS Issue 01/12/2016

We are seeing some oddness on one of our LNS routers which terminates some of our broadband circuits. We believe this is only affecting our management access and not the service provided over this.

We are working with the vendor to understand this and hopefully resolve this. Assuming this is not customer affecting we may need to reboot this LNS later this evening causing a brief network blip as the sessions re-connect.

IF we find this is affecting service earlier we may have to perform the reboot earlier. We will update this as we know more

 

UPDATE: issue fixed: VOIP SIP issues –inbound calls failing

UPDATE:

Divert Service Failures
Details: SIP Diverts are now working as normal and our engineers will closely monitor our VoIP network for any re-occurrences. If you were affected by the issue please retest and if the problem is still present contact our Support Team.

One of our suppliers is aware of a network problem as below. We’ll update here as they troubleshoot this. In the meantime, please accept our apologies if your circuits are affected.

Network Affected: VoIP
Problem Time: Wed 19th Oct 2016 at 9:30 am
Estimate Resolve Time: Wed 19th Oct 2016 at 10:00 am
What Does It Affect: Customers using SIP divert service
Event Overview: Divert Service Failures

Details: Some of our customers may be experiencing problems with our SIP Trunk Divert Service where inbound calls are failing. Our engineers are currently investigating and there will be further updates shortly.

Now’s the time to migrate to Merula to stop a broadband meltdown

On Tuesday 13th September, Apple releases the new version of iOS v10 following the launch of their new iPhone 7, followed not long afterwards by macOS Sierra, the new version of their desktop operating system, on 20th September.

We expect there to be a significant up-tick in traffic because of this, both through the whole day and probably well into the following ones.

We have plenty of spare capacity within our network and don’t envisage any problems directly affecting circuits supplied by us but the nationwide backhaul providers will be under some pressure, so be aware that transit may be slower than usual until this traffic dies down naturally.

There is still time to move to one of our fantastic unlimited tariffs before this onslaught hits!

If you’d like to upgrade we can offer you a FREE migrate from ADSL or another FTTC supplier so please get in touch straight away.

Email us using this link or call our free sales line on 0800 298 2375.

Issue with post.merula.net

Our primary outgoing smart mail server was down for a short while from approx 2pm due to a customers PC becoming compromised and sending a very high level of spam. We paused delivery on this server while the affected emails where removed from the mail queue to minimise the risk of the sever being black listed.

Mail delivery has now been re-enabled. While clearing the mail queue there is a small possibility that email sent just before the incident may not have been sent. If you are awaiting a reply to an email and are not sure it is probably safer to re-send just in case the email was not received.

We are sorry for the slow updated but we where concentrating on resolving this issue and did not anticipate the mail queue clearing to take so long

If you are still seeing any issues please drop an email to support as normal or call us on 0845 330 0666

Notification of Planned Work: 12th August Telehouse North – Virgin Media Business

We need to let you know about some maintenance work that will be taking place on our network. We will be upgrading one of our network back-haul links into the VMB node at our London, Telehouse North site.

Planned Work Start (Local UK): 12/08/2016 00:01 Planned Work End (Local UK): 12/08/2016 06:01

Impact: There will be a loss of service at some point during the timeframe stated above whilst we complete the maintenance work. You will see several interruptions to your service during the 2 hour outage window. We have planned and believe that all circuits will automatically return to service after the work is completed

Only those circuits supplied via VMB will be affected. Please email into support in the normal manner if you have any questions.

[CLOSED] OUTAGE: VOIP service

[update 17:40]

We believe that all connections have now been restored. If you still have VOIP problems, please raise a ticket in the usual manner.

We apologise for this down-time and are actively investigating alternatives and fail-over solutions as this is the second such outage in a few months.

[update: 16:00]

We understand that services are slowly being restored. This may take some time so please bear with us — we’re in the hands of the external supplier here. Further updates will follow as we get them through from the supplier network.

[update 14:52]

The supplier advises that the incident currently affecting their network is down to a Denial of service attack. They are now working with transit vendors to stop the attack and restore the network. Further updates will follow.

[update at 13:49]

Please be advised that the supplier is continuing to investigate the cause of this issue and apologise to all our customers who are affected by this. Further updates will follow.

We’re aware of issue affecting our core supplier which has dropped all of our VOIP circuits including our own PBX. There is no time to fix yet but we’ll update this ticket as we know more.