403 Forbidden - This service is not available from your country

[GoogleCodeExporter]

We are experiencing the same problem as issue #197, Our Digital Ocean server in 
Frankfurt reports 403 Forbidden { "code" : 403, "errors" : [ { "domain" : 
"global", "message" : "This service is not available from your country", 
"reason" : "countryBlocked" } ], "message" : "This service is not available 
from your country" }

No changes have been made on our part. Our IP is 46.101.250.54

What steps will reproduce the problem?
1. Create a Droplet in Frankfurt 1
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Ubuntu 14.04 LTS LEMP server

Please provide any additional information below.
At first we thought this was a deliberate severing of the analytics data 
because of the judgement in Court Justice of Europe which came one day before 
this issue happened. But the service still works from other IP:s in Germany and 
Netherlands so I think we can rule out that.

Original issue reported on code.google.com by nik...@lynks.se on 11 Oct 2015 at 7:06

[GoogleCodeExporter]

Hi, apologies for the late response; we're working on updating our support 
policy to avoid letting issues on this tracker fall through the cracks.

Is this still an issue for you?  If so, could you please copy the results of a 
traceroute to bigquery.cloud.google.com here?  From my perspective, it looks 
like packets to the IP you gave are being routed through New York -> London -> 
Paris -> Frankfurt.

Original comment by thomasp...@google.com on 24 Nov 2015 at 8:40

• Changed state: Accepted

[GoogleCodeExporter]

Hi Thomas
This is still an issue. Here is a trace route for you:

~# traceroute bigquery.cloud.google.com
traceroute to bigquery.cloud.google.com (173.194.113.0), 30 hops max, 60 byte 
packets
 1  46.101.128.253 (46.101.128.253)  0.619 ms  0.577 ms  0.553 ms
 2  5.101.109.26 (5.101.109.26)  0.519 ms 5.101.109.22 (5.101.109.22)  0.418 ms  0.473 ms
 3  de-cix10.net.google.com (80.81.192.108)  0.472 ms  0.461 ms 5.101.109.21 (5.101.109.21)  0.414 ms
 4  de-cix10.net.google.com (80.81.192.108)  0.400 ms  0.375 ms 216.239.50.154 (216.239.50.154)  0.602 ms
 5  209.85.242.185 (209.85.242.185)  1.162 ms 216.239.50.154 (216.239.50.154)  0.620 ms  0.592 ms
 6  209.85.242.185 (209.85.242.185)  1.270 ms  1.110 ms fra02s19-in-f0.1e100.net (173.194.113.0)  0.667 ms

Original comment by nik...@lynks.se on 24 Nov 2015 at 8:52

[GoogleCodeExporter]

Hi again Thomas,
I can't say for sure when this started working again. But I believe it was in 
the last three-four days. Is there a way to avoid these errors in the future? A 
paid support line or anything to avoid these awfully long waits?

Original comment by nik...@lynks.se on 8 Dec 2015 at 2:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

My sincere apologies - your reply came in when I was cleaning out the backlog 
of open and unhandled issues on this issue tracker, and I'm afraid I didn't see 
your reply amongst all of the other messages I was getting from the tracker.  
I'm sorry about that!

At some point next year, the issue tracker here (code.google.com) will be 
replaced with something that integrates better with our internal issue tracker, 
which should prevent messages from falling through the cracks.

Google does have paid support, which gives you email and telephone access to 
support staff : https://cloud.google.com/support/#comparison

The other venue I can recommend for support is Stack Overflow; BigQuery 
engineers monitor issues tagged "google-bigquery".

Overview of options is here : https://cloud.google.com/bigquery/support

Back to your original issue - thanks for that trace, I will dig into the 
country handling code, or pass the issue off to our oncall.

Best,
Thomas

Original comment by thomasp...@google.com on 8 Dec 2015 at 5:15

[GoogleCodeExporter]

I've opened a ticket with our API hosting infrastructure team and will let you 
know if they require any further information.

Original comment by thomasp...@google.com on 8 Dec 2015 at 5:26

[GoogleCodeExporter]

Thanks Thomas,
About a week before I reported this issue I followed the instructions I found 
here: 
http://stackoverflow.com/questions/26485851/google-contacts-api-responds-with-co
untryblock-error to report the IP but nothing happened, which is how I found 
myself here.

Original comment by nik...@lynks.se on 8 Dec 2015 at 5:29

[GoogleCodeExporter]

Hm; API hosting infrastructure is a different team from the one that the 
gentleman who responded on that SO issue works for, so perhaps we'll have 
better luck with my ticket.  I will add that link to my ticket for context, 
though, since it's also referencing a DE server.

Original comment by thomasp...@google.com on 8 Dec 2015 at 5:37

[GoogleCodeExporter]

I have gotten confirmation that some German IP addresses were miscategorized as 
being from a blocked region in an October ipGeo configuration build.  I do see 
one affected example also on the same A netblock as your server.

The API serving infrastructure only updates this configuration periodically / 
incrementally, so it's very possible that it was stale through November; I've 
asked for some more details and will update you if I find any further answers.

If this crops up again, please reach out to us on Stack Overflow - since 
blocked IP ranges may affect multiple customers, I think that should be an 
appropriate topic for SO.

Resolving for now, but I will update this issue if I get positive confirmation 
for your IP from Oct / Nov.  Thanks!

Original comment by thomasp...@google.com on 8 Dec 2015 at 6:44

• Changed state: Done