Buzz API

Hello Joel!

We are not encountering a system outage. If you are comfortable sharing reproduction steps to this public forum that will allow us to encounter the reported behavior, that will be helpful. Otherwise, I encourage reaching out to your organization's authorized support contact to report this behavior.

Thanks, and please let me know if you have any other questions about this! 

I'm currently seeing this error, when I try to connect to the buzz API from an AWS instance. This started around the same time as Joel's post.

curl 'https://gls.api.agilixbuzz.com/cmd?cmd=getstatus'
curl: (6) Could not resolve host: gls.api.agilixbuzz.com

curl 'https://gls.agilix.com/cmd?cmd=getstatus'
curl: (6) Could not resolve host: gls.agilix.com

curl `https://api.agilixbuzz.com/cmd?cmd=getstatus` does work. The 'gls' prefix is the problem. Did you update things on your part recently, either routing or actual hosting?

nslookup gls.agilix.com
Server: 10.0.0.2
Address: 10.0.0.2#53
Non-authoritative answer:
gls.agilix.com canonical name = gls.api.agilixbuzz.com.
gls.api.agilixbuzz.com canonical name = *.api.agilixbuzz.com.cdn.cloudflare.net.
*.api.agilixbuzz.com.cdn.cloudflare.net canonical name = webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com.
Name: webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com
Address: 34.226.83.75
Name: webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com
Address: 35.169.37.233
Name: webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com
Address: 3.218.57.86
Name: webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com
Address: 54.147.125.67
Name: webops-multitenant-buzzapi-287340637.us-east-1.elb.amazonaws.com
Address: 54.84.170.155

nslookup api.agilixbuzz.com
Server: 10.0.0.2
Address: 10.0.0.2#53
Non-authoritative answer:
api.agilixbuzz.com canonical name = api.agilixbuzz.com.cdn.cloudflare.net.
Name: api.agilixbuzz.com.cdn.cloudflare.net
Address: 54.147.125.67
Name: api.agilixbuzz.com.cdn.cloudflare.net
Address: 3.218.57.86
Name: api.agilixbuzz.com.cdn.cloudflare.net
Address: 54.84.170.155
Name: api.agilixbuzz.com.cdn.cloudflare.net
Address: 35.169.37.233
Name: api.agilixbuzz.com.cdn.cloudflare.net
Address: 34.226.83.75

Tony Herr the https://gls.api.agilixbuzz.com/cmd?cmd=getstatus request and the GLS endpoint does appear to be working. However, I would recommend that calls point to the https://api.agilixbuzz.com/ going forward. Our API documentation is located at: https://api.agilixbuzz.com/docs/#!/Concept/Overview

Brian Williams

Hi Brian,
Yes, I know the endpoint works outside of an AWS ec2 instance. I was wondering what you've changed recently, either routing or DNS or actual hosting. Our setup has been running for quite a few years (hence the old endpoints), and hasn't changed recently. I was able to update the endpoints in our service, once I tracked down the problem. But if other people are reporting problems today, they could be having the same issue.