>>> It surprises that important sites don't do mirroring.
>> depends on what you mean by 'mirroring.' think latency.
> Though a best effort to mirror would be acceptable. Maybe not up to
> the minute but at least a recovery.
depends on if the writer has to wait for it to hit the spinning oxide
On Thu, Mar 11, 2021 at 7:40 PM Randy Bush wrote:
> It surprises that important sites don't do mirroring.
>
> depends on what you mean by 'mirroring.' think latency.
>
> randy
> --
>
> Though a best effort to mirror would be acceptable. Maybe not up to the
> minute
> It surprises that important sites don't do mirroring.
depends on what you mean by 'mirroring.' think latency.
randy
---
ra...@psg.com
`gpg --locate-external-keys --auto-key-locate wkd ra...@psg.com`
signatures are back thanks to dmarc header mangling
There are plenty of websites still down: https://www.centrepompidou.fr/en/.
It surprises that important sites don't do mirroring.
-R.
From: Johann
Sent: Friday, March 12, 2021 12:41 AM
To: Rod Beck
Cc: Randy Bush ; Lukas Tribus ; Eilers, Laura via
NANOG
Several government websites have been impacted by fire. But >90% was
operationnel during the same day after the incident.
There are DRP (seems to be working) and backups in other datacenters. There
must remain exceptions or minor things broken.
But I think it's a pretty good result.
Johann
Le
It is terrible timing with the company planning an IPO and also because the
French government has heavily backed OVH. I think some government websites went
down. France has a statist tradition that leads it to get involved in
industries where has no expertise.
So this company (Global Resource Systems, LLC) was formed on 2020-10-13 and
ARIN assigned AS8003 to them even earlier than it.
Here's a simple timeline in case anyone want to have a check:
9/8/2020 GLOBAL RESOURCE SYSTEMS, LLC registered in Delaware
9/10/2020 Nameserver of grscorp.com was
On 3/11/21 2:28 PM, Jared Brown wrote:
Out of interest, why does it take multiple weeks to edit a GEO IP entry?
I have no idea /why/. I only know that it /is/.
I /assume/ -- from a place of ignorance about the innards of the process
-- that there is validation and manual approval. I also
Grant Taylor wrote:
> The process takes multiple weeks.
Out of interest, why does it take multiple weeks to edit a GEO IP entry?
I wonder why Google even has this problem at all. If you've so much as looked
at Google maps or used any app that uses location services then Google knows
with a
In the 1990s, I spent long time researching and talking to people about
the history of the old Automated Data Processing room code requirements.
You can tell by the terminology "Automated Data Processing" the age of the
original requirements. IBM helped write the original requirements in the
On 3/11/21 1:05 PM, Josh Luthman wrote:
His email: Mar 8, 2021, 10:08 AM (3 days ago)
The current date and time: 3:03 PM Thursday, March 11, 2021 (EST)
The process takes multiple weeks.
You do the math.
My email with recommendations: 10:23 AM Thursday, March 11, 2021 (MST)
The current date
From: George Herbert
...Interesting overview of fire damage.
I remember many years ago spec'ing a machine room at BU and coming to
loggerheads with the VP of building and grounds.
He (well, their rules) wanted low-temp sprinkler triggers, I wanted
the high-temp ones (I forget but I think
He looks sooo tired.
On 3/11/21 12:57 PM, Josh Luthman wrote:
The lack of response to the problem from Google's team is the
knowledge that we're working with.
It may be the knowledge that /you/ are working with. /I/ am working
with different knowledge.
As stated in another reply, "I know / have witnessed
>> Statement (in French) from Octave Klaba, containing some discussion
>> of the development of the fire (starts at ~ 4:30):
>> https://www.ovh.com/fr/images/sbg/index-fr.html
> English:
> https://www.ovh.com/fr/images/sbg/index-en.html
and a few hundred of us hoping we never have to stand in
>How do you know that the OP's problem hasn't been resolved?
I asked him. He said "no". Do we have to debate the opinion of fixed or
what no means?
>Presuming the OP did leverage the suggestions that I provided, how can
you say "no resolution" when it's been ~2 hours for a process that I
I think the distinction needs to be made between some number of {company}
employees and the effectiveness of the organization.
One, two, ten, or fifty dedicated employees working on the problem doesn't make
up for management that doesn't allocate appropriate resources to solve the
problem.
The lack of response to the problem from Google's team is the
knowledge that we're working with. What more do you need to know? If it
quacks like a duck, walks like a duck, and looks like a duck, it's probably
a duck. You don't need a DNA test.
You're entitled to your opinion just as the rest
On 3/11/21 12:28 PM, Josh Luthman wrote:
Based on how difficult it is to correct their data for them at no
charge, I'm not sure he's entirely wrong in that statement.
Difficult of doing something is not directly related to people's
willingness / desire to do it.
I can guarantee you that
>
> Based on how difficult it is to correct their data for them at no charge,
> I'm not sure he's entirely wrong in that statement.
>
No, it's still wrong.
Stating that Google's team 'doesn't want to improve things' , while also
having zero knowledge of the reasons why the current issues are
Based on how difficult it is to correct their data for them at no charge,
I'm not sure he's entirely wrong in that statement.
The fact that this thread exists, the latest of multiple, and has ended in
no resolution to the problem once again is a testament to how Google
responds to this problem.
On 3/11/21 2:36 AM, William Guo wrote:
but they don't wanna improve it for some reason.
That is both unfair and wrong.
I know for a fact that they do want their internal GeoIP to be as
accurate as possible and that they do want to improve the inaccuracies
if and when possible.
I have
On Thu, 11 Mar 2021 at 18:10, Enno Rey wrote:
>
> Statement (in French) from Octave Klaba, containing some discussion of the
> development of the fire (starts at ~ 4:30):
>
> https://www.ovh.com/fr/images/sbg/index-fr.html
English:
https://www.ovh.com/fr/images/sbg/index-en.html
> On Mar 11, 2021, at 10:41 AM, Sean Donelan wrote:
>
> If you pump 100s of megawatts of energy into a confined space (i.e. a large
> data center), and there is an uncontrolled release of that energy (i.e. a
> fire), that's a lot of energy which is going to go somewhere.
> Stored energy,
> On Mar 11, 2021, at 5:06 AM, Matt Harris wrote:
>
> There are plenty of effective options besides environmentally-destructive
> Halon, dangerous-to-equipment water sprinkler, or dangerous-to-personnel CO2
> for fire suppression these days. Some of the most common today are foam
> systems
If you pump 100s of megawatts of energy into a confined space (i.e. a
large data center), and there is an uncontrolled release of that energy
(i.e. a fire), that's a lot of energy which is going to go somewhere.
Stored energy, batteries, backup fuel for generators, server plastic, etc.
There is
On Thu, Mar 11, 2021 at 10:54 AM j k wrote:
>
> Two questions...
>
> 1. How many on this list already have dual-stack or IPv6 only in operation?
we're coming up on the 10yr anniversary of 'world ipv6 day'.. so I
would HOPE 'lots' :)
probably that's not entirely a good 'hope' :(
> 2. If you are
>
> https://us.ovhcloud.com/about/company/green-tech
>
> Further I conjecture that a halon system would not be feasible in such a
> structure.
>
> Daniel
>
> There are plenty of effective options besides environmentally-destructive
> Halon, dangerous-to-equipment water sprinkler, or
On Thu, Mar 11, 2021 at 10:45 AM Dale W. Carder wrote:
> Sadly, the foams are not without environmental impact either with
> respect to PFAS.
what's the trade off on environmental impact for:
"foam fire retardant" (or halon or ...)
vs:
"Burning plastics and other carcinogen like materials"
Two questions...
1. How many on this list already have dual-stack or IPv6 only in operation?
2. If you are running IPv4 only, and a major service was to switch to IPv6
only,..
a. How fast would you move to a dual-stack of IPv6 only?
b. What would it impact your customers?
c. How
Thus spake Matt Harris (m...@netfire.net) on Thu, Mar 11, 2021 at 05:06:46AM
-0600:
>
> There are plenty of effective options besides environmentally-destructive
> Halon, dangerous-to-equipment water sprinkler, or dangerous-to-personnel
> CO2 for fire suppression these days. Some of the most
Google honour https://tools.ietf.org/html/rfc8805 Which they also authored.
A bunch of people are proposing a geofeed: RPSL marker to catalog how
to find the feed.
-G
On Thu, Mar 11, 2021 at 7:38 PM William Guo wrote:
>
> Google has its internal GeoIP team.
>
> But the data quality is not so
I scratch it out to hiding in plain sight...
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.netFax: 514-990-9443
On 3/11/21 9:14 AM, Filip
> Again: all conjecture, which seems to be tolerated here. ;-)
It's all good food for thoughts! It's important to learn from these
things, because I (and I expect many others) assumed that fire
suppression systems would prevent something like this from happening.
It is good to think and talk
Contacted HE NOC earlier regarding these announcements, they are
"legitimate".
Filip
On 11/03/2021 14:56, Javier Henderson wrote:
On Mar 11, 2021, at 8:43 AM, Eric Dugas via NANOG wrote:
I would be really curious to see the LOA presented to AS6939 to announce 54
million IPs out of
On 11 Mar 2021, at 11:46, Daniel Karrenberg wrote:
… Further I conjecture that a halon system would not be feasible in
such a structure. …
Several of you have pointed out to me at varying level of politeness
that ‘halon’ is no longer used. Sometimes I cannot hep but reveal my
age … ;-)
> On Mar 11, 2021, at 8:43 AM, Eric Dugas via NANOG wrote:
>
> I would be really curious to see the LOA presented to AS6939 to announce 54
> million IPs out of government IP space and what type of verification was done
> because it doesn't seem legit at all.
Did you try calling the number
Single-homed on AS6939, no website setup on gsrcorp.com. (gsrcorp.com)
The address listed is in Plantation, PL and shows is a typical commercial
office building. You can even get virtual office address here:
https://www.davincivirtual.com/loc/us/florida/plantation-virtual-offices/facility-2492
Hi Folks,
Just noticed that almost all DOD prefixes (7.0.0.0/8,11.0.0.0/8,22.0.0.0/8
and bunch of /22s) are now announced under AS8003 (GRSCORP) which was just
formed a few months ago.
It looks so suspicious. Does anyone know if it's authorized?
Regards,
Siyuan
Matt Harris|Infrastructure Lead
816-256-5446|Direct
Looking for something?
Helpdesk Portal|Email Support|Billing Portal
We build and deliver end-to-end IT solutions.
On Thu, Mar 11, 2021 at 4:46 AM Daniel Karrenberg wrote:
> Maybe the innovative ‘green’ design had something to do with the
>
Hi Daniel,
>
> Tracing it back to the originator of the route is of course a good first step.
Yes, we have done that and the results were not good.
The company that created the LOA is registered in the Seychelles and they have
IPs that were/are being revoked by Afrinic
remarks:* * * *
On 10 Mar 2021, at 16:42, Andy Ringsmuth wrote:
Sad to see of course, but also a little surprising that fire
suppression systems didn’t, well, suppress the fire.
Maybe the innovative ‘green’ design had something to do with the
rapid spread of the fire and the way fire suppression was
It is amazing that they can burn so well. Would never have imagined it.
Regards,
Roderick.
From: NANOG on behalf
of George Herbert
Sent: Thursday, March 11, 2021 11:37 AM
To: Andy Ringsmuth
Cc: nanog@nanog.org list
Subject: Re: OVH datacenter SBG2 in
Sent from my iPhone
> On Mar 10, 2021, at 7:45 AM, Andy Ringsmuth wrote:
>
> Sad to see of course, but also a little surprising that fire suppression
> systems didn’t, well, suppress the fire.
>
> Unless they didn’t exist?
I am assuming you haven’t had a real datacenter fire before.
I’ve
Tracing it back to the originator of the route is of course a good first
step.
I would send an FYI to the RIR that allocated the prefix; preferably
after the initial investigation established that it was not a genuine
mistake. In that message I would make very clear if any action is
Google has its internal GeoIP team.
But the data quality is not so good, but they don't wanna improve it for
some reason.
On Mon, Mar 8, 2021 at 8:00 AM Nate Burke wrote:
> If you find out, let me know the secret sauce. I've had a ticket open
> with YoutubeTV for 7 months and they can't get
46 matches
Mail list logo
