@ajkuma Hi, We experience that notifications take several minutes to send out to devices - this applies to both APNS and GCM. We can not determine what may be wrong by just looking at "Monitor | Metrics". This happened simultaneously in all our environments (Dev, Test and Prod). The error started about two hours ago and we are in the North Europe region. We use Basic price tier for the production environment. No reports through https://status.azure.com/en-us/status yet. (I'm waiting to be able to create a support ticket in Azure, but I do not have rights to do so yet.) I am very grateful for quick answers. Br, Crippe

@Christer Alm , Apologies for any inconvenience with this. I'd been checking on this internally. A very few customers may have experienced this impact in North Europe region and the issue was resolved within few minutes. Kindly let me know in case you're still experiencing this issue. I'll reach out to privately to fetch more details on your subscription.

Notification Hubs - North Europe - problems with notifications that take several minutes to reach a device

Accepted answer

ajkuma 26,636 Reputation points Microsoft Employee

2021-03-04T12:42:02.947+00:00

@Christer Alm , Apologies for any inconvenience with this.

I'd been checking on this internally. A very few customers may have experienced this impact in North Europe region and the issue was resolved within few minutes.
Kindly let me know in case you're still experiencing this issue. I'll reach out to privately to fetch more details on your subscription.
Please sign in to rate this answer.

1 person found this answer helpful.
Christer Alm 61 Reputation points

2021-03-04T14:06:42.407+00:00

Update

After a few hours, the push notifications started working normally. But I still do not know what the problem was.

I have now had the opportunity to create a support ticket.

ajkuma 26,636 Reputation points Microsoft Employee

2021-03-04T21:13:54.67+00:00

@Christer Alm , Thanks for the update. Glad to know that the issue is resolved.

As mentioned in this doc, because of the nature of push notifications (they are delivered by an external, platform-specific PNS), there is no latency guarantee. So, I would suggest you consider moving to direct send to avoid any noisy neighbor latency issue, for workloads sensitive to end-to-end latency.’

I have also shared this feedback with our product engineering team. I understand the concern, once again apologies for all the inconvenience

Christer Alm 61 Reputation points

2021-03-09T08:37:33.19+00:00

Hi,

Now I know a little more. It was a fault in a "scale unit" that affected just our environments. It has been fixed and should not be able to happen again.

Br,
Crippe

Christer Alm 61 Reputation points

2021-03-09T08:41:36.36+00:00

Hello @ajkuma

What I was looking for here was latency within Notification Hubs, from the time a notice arrives at NH to it being sent to a third party. But just as you have mentioned, there are no such values documented.

Br,
Crippe

ajkuma 26,636 Reputation points Microsoft Employee

2021-03-09T10:16:28.893+00:00

ChristerAlm-3908, Thanks for the update. It could rarely happen, but it was identified and fixed immediately. Once, again apologies for any inconvenience with this.

Also, additionally info on 'Push notification service issues'/latency (there is no such specific value):
Because platform notification services are robust, notifications tend to reach devices in a few seconds. If the push notification service is throttling, Notification Hubs applies an exponential back-off strategy. If the push notification service remains unreachable for 30 minutes, there's a policy in place to expire and drop the messages permanently.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Notification Hubs - North Europe - problems with notifications that take several minutes to reach a device

0 additional answers

Your answer