502 errors today - anyone else?

[Mike Sullivan]

I have had a couple of customers with 502 (Bad Gateway) errors today on previously good queries. Is anyone else seeing this? Are Google's servers overloaded for some reason (1st of the month reporting overload?)

[Jeetendra Soneja]

Hi,

Are you still seeing the errors ? We recently discovered a couple of minor issues with queries that use regular expressions in filters or advanced segments, which could cause server errors. We are working on fixing these.

If you are still seeing the errors, can you share the queries that you are getting the errors for ?

Thanks,

Jeetendra.

[Rhys Campbell]

I'm seeing these today as well.

"The remote server returned an error: (502) Bad Gateway."

On the following two queries...

&dimensions=ga%3Adate%2Cga%3Abrowser%2Cga%3AbrowserVersion%2Cga
%3AisMobile%2Cga%3AjavaEnabled%2Cga%3AoperatingSystem%2Cga
%3AoperatingSystemVersion&metrics=ga%3Avisits&segment=gaid%3A
%3A-1&sort=ga%3Adate&start-date=2011-12-27&end-date=2012-02-01&start-
index=1&max-results=9999

&dimensions=ga%3Adate&metrics=ga%3Avisits%2Cga%3Apageviews%2Cga
%3AnewVisits%2Cga%3Aentrances%2Cga%3Aexits%2Cga%3Abounces%2Cga
%3AtimeOnPage%2Cga%3AtimeOnSite&segment=gaid%3A%3A-1&sort=ga
%3Adate&start-date=2012-01-31&end-date=2012-02-01&start-index=1&max-
results=9999

[Mike Sullivan]

no regular expressions, but there was a filter in one of the queries:

&segment=gaid::-1&start-date=2012-01-01&end-date=2012-01-31&max-results=20&dimensions=ga:campaign&metrics=ga:visits,ga:pageviewsPerVisit,ga:avgTimeOnSite,ga:percentNewVisits,ga:visitBounceRate&filters=ga:campaign!@(not+set)&sort=-ga:visits,ga:campaign

[Mike Sullivan]

and yet another query from a different customer with nothing special at all:

&start-date=2012-01-01&end-date=2012-01-31&max-results=10000&dimensions=ga:date,ga:hostname,ga:browser&metrics=ga:visits,ga:visitors,ga:pageviews,ga:timeOnSite,ga:visitBounceRate,ga:newVisits

[HighCat]

Hi,

This query gives me 502 today:
start-date=2012-01-23&start-index=1&segment=gaid%3A%3A-1&ids=ga
%3A35519698&metrics=ga%3Avisits%2Cga%3Abounces&end-date=2012-02-02

But these, with different segments are working:
start-date=2012-01-23&start-index=1&segment=gaid%3A%3A-6&ids=ga
%3A35519698&metrics=ga%3Avisits%2Cga%3Abounces&end-date=2012-02-02
start-date=2012-01-23&start-index=1&segment=gaid%3A%3A-8&ids=ga
%3A35519698&metrics=ga%3Avisits%2Cga%3Abounces&end-date=2012-02-02
start-date=2012-01-23&start-index=1&segment=gaid%3A%3A-7&ids=ga
%3A35519698&metrics=ga%3Avisits%2Cga%3Abounces&end-date=2012-02-02

[jasper]

We are experiencing the same issue. The segment (e.g. "...segment%3Dgaid%253A%253A-1...") seems to be responsible for the error. Leaving it out is not really an option for us though.

[Nick]

We used segments as well. It giving Fetching error on Excel and
without segments simple query works fine.

[Jeetendra S.]

Hi all,

Thanks for your feedback. Yes, we discovered an issue with segments
and we are working on a fix. There's another outstanding issue that
causes an error with certain kinds of regular expressions in a filter.

We are actively working on fixing both these issues. Will keep you
guys posted on these.

Sorry for the inconvenience.

Jeetendra.