-
Notifications
You must be signed in to change notification settings - Fork 7
Are you guys still in business? #5
Comments
+1 I am also having issues - I receive a 503 Service Temporarily Unavailable message when sending an API request, and checking the status link ( |
Hi folks, I'm one of the co-founders of Geocode Earth and one of the creators and maintainers of the Pelias open source project that Positionstack uses to provide their services. If either of you, or someone else, need a geocoding service while dealing with what is hopefully only a temporary outage here, we'd be happy to help you out with service through Geocode Earth. For small usage our free trial should be able to get you started immediately, but don't hesitate to shoot us an email at [email protected] if not. We'd hate to see people's business impacted right now. |
Not working here in Sweden, perfect until 1 of may. Totally down. |
Positionstack has been down since yesterday. Do you have a timeline from when it will come back? |
Den 2021-06-18 kl. 15:08, skrev AschHarwood:
Positionstack has been down since yesterday. Do you have a timeline from when it will come back?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARJ6PNST5DKKUIVDFI6XNQ3TTNANPANCNFSM434GJXPQ>.
I'm not using Positionstack anymore.
I use LocationIQ instead. Works like a dream.
…--
*Mvh/Mbh,
Ralph Höglund
Webbutveckling, programmering
0418-10 029
073-928 14 25 <http://comprog.se>*
|
Any update regarding about the downtime? The system has been down since last week Thursday. |
I just signed up to use the PositionStack API this week and it's totally unreliable. I'm getting cloudflare error messages. Can I get a refund? I need a reliable API. |
Their services are still sadly terrible in 2023. |
Your service has been down with 500 errors since yesterday and I'm not getting a response in my support tickets on zendesk.
Is there anyone that could comment on the downtime?
The text was updated successfully, but these errors were encountered: