Reviews stars filter
Amazon Web Services, Inc. insights
Updated: 16 May 2022 | Next update: 23 May 2022Lost to
Total lost 42,437,643 to:
- 3,461,219
- 1,756,645
- 1,174,411
- 937,219
- 757,216
- 630,167
- 617,187
- 531,313
- 518,527
- 425,884
Terminated domains
12,348,572
Gained from
Total Gained 39,873,893 from:
- 3,704,566
- 1,843,661
- 1,837,494
- 1,090,010
Webair Internet Development Company Inc.
863,513- 722,101
- 661,307
- 592,993
- 510,486
- 430,510
Registered domains
16,640,007
G
Lost to
Total lost 42,437,643 to:
- 3,461,219
- 1,756,645
- 1,174,411
- 937,219
- 757,216
- 630,167
- 617,187
- 531,313
- 518,527
- 425,884
Terminated domains
12,348,572
Gained from
Total Gained 39,873,893 from:
- 3,704,566
- 1,843,661
- 1,837,494
- 1,090,010
Webair Internet Development Company Inc.
863,513- 722,101
- 661,307
- 592,993
- 510,486
- 430,510
Registered domains
16,640,007
Report inaccuracy
Amazon Web Services, Inc. TLDs
Total Domains:
8,860,718
G
G
Steve Bonham
gcorelabs.comaws.amazon.com
G Core
We have been working with G Core for 3 years now. We rent hosting from this company and, as we expanded to several countries, we connected a CDN. At the end of summer, during a major DDoS attack, the server was shut down for more than a day. This is unacceptable for our site, users could not enter the store or find out the order status. After that, we connected a special protection, also from G Core. While we have taken the starting plan, in six months I will additionally analyze the situation and reports. If, according to statistics, there are many new reflected attacks, we will think towards expanding the protection functions. It took no more than an hour to connect the protection, no special actions are required. We will check how the system works during new attacks.