Google+ to shut down following bug that exposed 500K profiles

Google to close Google+ after 7 years: A look back at the impact it once had on Google search

This should come as no surprise, Google is closing down Google+ over lack of use and security issues.

What Happened to Google+? Why the Social Network Shut Down | EM360Tech

This article explores what happened to Google+, explaining why Google's infamous social Circles never took off in the golden age of online social media.

Facebook will shut down its spyware VPN app Onavo | TechCrunch

Facebook will end its unpaid market research programs and proactively take its Onavo VPN app off the Google Play store in the wake of backlash following

Incident Report: May 19, 2026- GCP Account Suspension

Railway experienced a platform-wide service disruption due to Google Cloud incorrectly placing our account in a suspended status. This resulted in a temporary loss of service for all GCP hosted infrastructure.

The new Security Checkup

Take 2 minutes to check your security status and get personalized tips to strengthen the security of your Google Account.

Keep Android Open

Your phone is about to stop being yours. In 2027, Google will block every Android app whose developer hasn't registered with them.

Google+  |  web.dev

We hit our goal of never downloading more than 60k of HTML, 60k of JavaScript and 60k of CSS at any one time!

Why does Google+ insist on having your real name?

Google+ is the latest social network to demand people's real names. But why do they need them?

Google can keep its Chrome browser but will be barred from exclusive contracts | Hacker News

GCP Suspension Outage: May 19th 2026 - Railway Central Station

Update: May 20th, 2026 - 03:57 AM EST, latest post mortem pending updates from Google: https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage Hello all, As part of our commitment to be as transparent as possible about the recent outage: https://status.railway.com/ (and any incident on the platform) we are summarizing what we know thus far- as well as some common questions that we have fielded thus far. _**We plan to update this thread with our official post-mortem once we have the details.**_ As it stands right now, we are working on getting everyone recovered. If not, a user can now redeploy and we will route your code to a healthy machine. We have our whole support team working getting workloads on Google Cloud hosts restored. Keep in mind, we are getting ratelimited by GH as our build pipeline is restoring to be fully healthy. **What we know:** Around 22:20 UTC, our Google Cloud account was placed into a "restricted" status hence removing all of our cloud overflow VMs, our CloudSQL instance, and our API. In removing our API, it removed a central dependency that affected all GCP host workloads, and then after our network route cache expired, then affecting all workloads hosted on the Railway platform. We don't have full knowledge as to why our account was suspended automatically. We got into contact at the start of incident and we remain in contact with the GCP engineering team as we root cause the issue. **FAQ:** **Q: "Doesn't Railway run it's own hardware?"** A: Yes, Railway runs hardware in 8 sites around 4 locations around the world. At the start of 2026, due to demand on our systems, we have bursted back onto the cloud on AWS and GCP. A subset of non-latency sensitive customers and Enterprise customers are using a public cloud for their hosts. However, when we migrated fully onto Metal in Mar. 2025, we kept our API and our DB on GCP as we felt that leaving that workload was well within our risk model. (Candidly: we didn't expect to get our cloud account to get removed via automated enforcement.) **Q: "Why does your API being down mean that my workload went down?"** A: Railway's API talks to our distributed edge which is a suite of proxies that we have all around the world. Each location at the edge maintains a routing table of DNS, however, the network team was in the middle of fully distributing the routing table to make it that each region was fully independent. Once the routing cache at the edge was expired, then all workloads were affected and not just GCP workloads. This is due to be rectified. **Q: "My workload is still down. What gives?"** A: We're seeing recovery in our API, builds, and deployments. If your service is having an issue, please try to give it a redeploy. We'll publish a public postmortem covering what happened when we're fully recovered. | Get Help with Railway

Tim Sweeney on Twitter / X

Google is opening up Android all the way with robust support for competing stores, competing payments, and a better deal for all developers. So, we've settled all of our disputes worldwide. THANKS GOOGLE! https://t.co/Dq6eXNnZd0— Tim Sweeney (@TimSweeneyEpic) March 4, 2026

Google accused of ‘predatory conduct’ over Gmail API withdrawal

Google has exploited a regulatory gap to withdraw access to the Gmail API, according to UK startup Gener8.

Is Google about to destroy the web?

Google says adding more AI to its search engine will rejuvenate the internet. Others predict an apocalypse for websites. One thing is clear: this era of online history is closing.

Google is its own worst enemy

In its bid to push AI, it’s destroying its products and trying to kill the web too