1
Completed

There is quite a bit of latency to the PushOver API

I noticed that there is quit a bit of latency on the PushOver API

I did a tracert on all IP's and I guess the server(s) are hosted in the US:

Tracing route to api.pushover.net [45.77.212.87]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.149.1
2 13 ms 10 ms 8 ms dhcp-077-248-253-001.chello.nl [77.248.253.1]
3 6 ms 11 ms 10 ms 212.142.54.29
4 14 ms 21 ms 11 ms asd-rc0001-cr101-be114-2.core.as33915.net [213.51.7.98]
5 18 ms 27 ms 15 ms nl-ams14a-ri1-ae50.core.as9143.net [213.51.64.58]
6 * 16 ms * 213.46.182.38
7 183 ms 181 ms 174 ms ae19.cr5-sea2.ip4.gtt.net [89.149.139.222]
8 172 ms 358 ms 186 ms ip4.gtt.net [72.29.200.42]

As notifications are send in the Netherlands and also delivered that is causes delays.

Roundtrip latency seems to be about 600-750ms. As PushOver only allows 2 connections that means that I can only transmit about 2.5 messages per second.

In my case I'm alerting a group of users based on a first responder alert and that not everyone gets their message at rougly the same time.

This might partially be mitigated by:

- allowing more than 2 connections and apply rate limiting instead of a connection limit. Could maybe still do a connection limit like 10 which aligns with I think the default http client limit to a server.

- have a european server that is for example hosted on `eu-west.api.pushover.net`

1 reply

1

Are you sending the same message to all of the users?  If so, you can send to multiple users in one request either by putting them in a group and sending to the group key as the user parameter, or by joining multiple user keys with commas as the user parameter.

Topic is closed for comments