IssueTracker

Hello Kévin

Thank you for contacting Google Cloud Platform Support. I understand you are having an issue with internal load balancing and I will do my best to advise you.

Internal load balancers are regional resources, the scope of an internal TCP/UDP load balancer is regional, not global. This means that an internal TCP/UDP load balancer cannot span multiple regions. Within a single region, the load balancer services all zones. [1]

A feature request exists to enable an internal load balancer which can handle requests from multiple regions[2]. But I can neither provide you with an ETA for its implementation, nor a guarantee that it will ever be supported. If you would like to create your own feature request, follow the link to Google issue tracker to search or create feature request [3].

Your VMs are able to talk to each other from one region to another as they are connected through the same VPC. Resources within a VPC network can communicate with one another using internal (private) IPv4 addresses, subject to applicable network firewall rules.[4] However, for ILB the behaviour is handled differently due to the regional nature of the ILB(s).

The reason VM instances attached to a network with a specific address mask getting assigned IP with /32 mask is a design requirement of GCP. However, let me explain why VM instances are assigned with the /32 mask on Google Compute Engine (GCE). Please note that the /32 is an artificial construct. The instance talks to the software defined network, which creates and manages the "real" subnets. So, it is really a link between the single address and the gateway for the subnet. As long as the link layer is there, communication is established, and everything works.

In addition to that, network masks are enforced at the network layer, not the host layer. This helps avoid generation of unnecessary broadcast traffic (which underlying network wouldn't distribute anyway), this might further clarify why VM instances are assigned with a /32 netmask, when they are attached to a subnet, for example, /24 mask.

I hope that makes things clearer for you. If you have any other questions or concerns about your issue, please do not hesitate to contact me by replying to this message. I will be more than happy to help at that time.

[1]ILB Scope: https://cloud.google.com/load-balancing/docs/internal/#protocols_scheme_and_scope
[2]Feature Request for multi-region ILB: https://issuetracker.google.com/111021512
[3]Create and Search feature requests: https://cloud.google.com/support/docs/issue-trackers#search_and_create_feature_requests_by_product
[4]VPC Specifications: https://cloud.google.com/vpc/docs/vpc#specifications

Thanks for your quick reply on ILB and thank you also for details on networking on gcp.

I hope that this feature request https://issuetracker.google.com/111021512 will be considered :).

I am surprised that it has been designed like this because it's a pretty big drawbacks compared to AWS for example.

Do you know if there is another solution for me to interconnect local service to another region except create loadbalancer in a dedicated instance ?

Thanks in advance,
Kévin
 

At the time of writing this, creating a dedicated instance which will serve as a load balancer between regions, is the best workable option for this type of scenario.

I have the exact same feature request to access ILB from multi regions. It would be great if Google can prioritize this feature. Thanks.

Hi, please take a look at my update to the public feature request:

https://b.corp.google.com/issues/111021512#comment37

You'll be pleased to note that GKE 1.16 allows you to annotate a service of type LoadBalancer such that it is both internal and globally accessible.  We can close out this issue now.

Same here, this was working always, now #N/A in many FRA items.

So we can hope for a fix? FRA ETFs seem to be all broken still e.g. FRA:VWGL

Most TSE REITs are still broken. They've been broken since May 2023.  Examples: TSE:BEP.UN, TSE:KEG.UN, TSE:REI.UN, TSE:HOT.UN

Now NYSE:FRT works fine.
thanks

What is up? since Monday July 17 no Data for ETF from Frankfurt on Google Finance and Google sheets. Before that the last price was from June 30!
Even worse, all my ETF in Portfolio now disappeared completely.
Please fix it soon.
thx.

FRA:EUNL, FRA:IS3N and FRA:IUSN still broken.

FRA: SXR8 is also an issue for me. Still an issue.

Just so it's not lost in the shuffle but the problem identified in https://issuetracker.google.com/issues/284822200 regarding Canadian REITs (which was closed as a duplicate and linked to this issue) is not only a problem with the GOOGLEFINANCE function but the tickers are completely missing from https://finance.google.com

ASX:CBA suddenly working today, both with GOOGLEFINANCE and https://www.google.com/finance/quote/CBA:ASX?hl=en.

Hey google guys, do we have an ETA for the fix? Thanks

Still not working: SXR8

FRA:DBZB still missing. Go Bard go!!!!

FRA:XMAW and FRA:IUSN are been broken too - I noticed the issue first on June 16th 2023

below ones are still not working :
IST:AKYHO
IST:AZTEK
IST:CRDFA
IST:MAKTK
IST:PENTA
IST:SDTTR

Same issue for all FRA:'s ETF's I'm tracking. Happens more often, but now it's been a while. Can't even find them on https://www.google.com/finance/ anymore. Seems to be disappeared? Just writing to make this ticket more relevant to solve.

Kindly fix these as well, thanks!
FRA:2B7K
FRA:AYEM
FRA:AYEW
FRA:XRS2
FRA:LYP6
FRA:LYQ7

FRA:SXR8  is an issue. Been like this for 2 weeks now. Thanks

We have been reporting the malfunctioning of the Google Finance application in #76403135 until it seemed that it was being "tracked" here.
Thanks very much for that although I fail to believe anything is being "tracked" at all, at least not by Google.

So, once more my two cents in this matter. Since about a month all tickers that are registered on the XETRA (Frankfurt Exchange) are not working in Google Finance. They have disappeared.
Examples:
FRA:NUKL
FRA:SXRJ
FRA:WTi2
FRA:IQQQ

And many more.

Hey, Google ignores us Canucks as well.

TSE     BIP.UN
TSE     BEP.UN
TSE     BEP.UN
TSE     BIP.UN
TSE     AP.UN

Broken for several months.

Same here for FRA:VGWD

Same here, GGG symbol is not working on the NYSE market

FRA:DBZB and FRA:SPPW also stopped working a week of two ago.

These 2 are returning N/A as well:
SPDR S&P Euro Dividend Aristocrats ETF  FRA:SPYW
SPDR S&P US Dividend Aristocrats ETF    FRA:SPYD

FRA:SXR8

SXR8 on the german XTRA  exchange

Also N/A both on website and google sheets.

Same for EPA:SEL

iShares MSCI ACWI UCITS ETF also stop working eta 2 weeks ago.

Ticker: IUSQ

Please fix also FRA:QDVE

FRA:EXSA returning N/A

Also N/A on website Google Finance

NYSE:PCOR does not work either.

Do we have an ETA for a fix?

For info - This issue is not with Sheets or GoogleFinance !!  The cause is due to severe errors within the Google Finance website !!!  There have been many, many reports submitted to the Finance site, over many months, most/all with no response as to the cause, and no correction.  Wish I knew how to escalate this to Google management!!!  cw

It's been months, since those ".UN" tickers returns #N/A:
TSE:CAR.UN
TSE:IIP.UN
TSE:BEP.UN

I mean... Stock market transactions take place in milliseconds, those days.

MONTHS!?
Google?! Hellooooooooooooooo!!

Well an ETA for a fix... do we have anyone of Google paying attention to this at all ? Google doesn't have support phone number you can call you know.

Would it be possible to escalate this issue? How shall I run my business with GOOGLE tools not running for weeks?

If you go to the Google Finance website there is "feedback" that you can send. I have done this several times over the past month but I never got any response to that.

Then there is this :
https://console.cloud.google.com/getting-started?_ga=2.62430060.1953452593.1690971730-1114924376.1690971730&pli=1

Here it is possible to create and escalate cases but it looks like that is for Cloud services

Same for ASX (NYSE:ASX)

Add nyse:nog to the list of dead tickers.  Would it kill jp..@google.com to post an update?  His last post was June 21 🤔