The new data center, located in Dammam, eastern Saudi Arabia, is a great option for customers who want to keep their site’s backend data housed within the Kingdom and those reaching out to a Saudi audience.

The addition of the Dammam data center (known as me-central2) puts Kinsta’s WordPress hosting services in 37 GCP data centers around the world. Damman is the second Middle East data center for Kinsta – the first being Tel Aviv, Israel (me-west1).

The Saudi data center is available now for those creating a new WordPress site within the MyKinsta dashboard. You can select Dammam as your target data center when you Add a Site in MyKinsta and choose to install WordPress, generate an empty environment, or request the migration of a website from another hosting company.

If you already have a WordPress site up and running in another data center and want to move it to Dammam, you can contact Support to request that change.

Why choose the Dammam data center?

Organizations in the Kingdom of Saudi Arabia are motivated to keep sensitive data—like website customer information—within the country. That makes the Dammam location perfect for their WordPress sites. However, anyone hoping to connect with a web audience in the region can take advantage of the proximity of the Dammam data center to minimize the impact of network latency on those connections.

You can use the free GCPing tool shown below to measure latency between your location and GCP data centers like Dammam’s around the world. By using a VPN service with a global footprint, you can simulate connections from locations where your site’s visitors might be.

Reach the world from the Dammam data center

A Dammam-homed website doesn’t have to cater only to visitors from the region. Kinsta’s Edge Caching service places web pages on the doorsteps of audiences around the world. Our Content Delivery Network does the same for web assets like images and files containing JavaScript code, CSS, and fonts.

Edge Caching and the CDN are free, thanks to Kinsta’s Cloudflare integration, which delivers cacheable components of your website to another 260+ data centers globally.

Not yet a Kinsta customer? Boost your global business today with a no-risk trial of a Kinsta hosting package.

The post Kinsta offers WordPress hosting from Google’s Saudi Arabia data center appeared first on Kinsta®.

These endpoints are designed to enhance your ability to manage content delivery and caching strategies directly through our API, providing more control and flexibility over your application’s performance and response times.

1. Application CDN

Kinsta’s Application Hosting offers a premium CDN service powered by Cloudflare at no extra cost. The CDN enhances security with an enterprise-level firewall and DDoS protection while leveraging Cloudflare’s expansive global network across 260+ locations in over 100 countries.

This allows for the efficient distribution of static assets, improving application performance. It caches files based on their extension, excluding files accessed with an Authorization header, and supports a wide range of file types.

The CDN is not enabled by default and requires activation/deactivation via a POST request to the CDN API endpoint.

CDN activation/deactivation

To use this endpoint, you need your application’s unique ID. You can obtain this programmatically by listing all applications associated with your Kinsta company, which provides essential details about each application.

With the application ID in hand, You can send a POST request to /applications/${application_id}/cdn/toggle-status, and it toggles the feature:

curl -i -X POST \
 'https://api.kinsta.com/v2/applications/{application_id}/cdn/toggle-status' \
 -H 'Authorization: Bearer '

Ensure you replace <YOUR_TOKEN_HERE> with your actual API key and {application_id} with the specific application ID.

2. Application Edge Cache

The Edge Caching feature for Kinsta Application Hosting enhances your application’s performance and speed by caching your application’s web pages across Cloudflare’s global network. This ensures cached responses are delivered from the closest location to your visitors.

Edge Caching does not handle static assets like image, JavaScript, and CSS files; these can be served through Kinsta’s CDN, which operates independently and provides an additional caching layer.

By default, Edge Caching is not enabled. To enable or disable Edge Caching for applications, send a POST request to the edge-cache API endpoint.

Edge Cache activation/deactivation

As with the CDN endpoint, you need an application ID to send this request. With the application ID in hand, send a POST request to /applications/${application_id}/edge-cache/toggle-status, and it toggles the feature:

curl -i -X POST \
 'https://api.kinsta.com/v2/applications/{application_id}/edge-cache/toggle-status' \
 -H 'Authorization: Bearer '

Ensure you replace <YOUR_TOKEN_HERE> with your actual API key and {application_id} with the specific application ID.

3. Clear application cache

The clear-cache API endpoint allows for the clearing of both CDN and Edge Cache, ensuring that any updates to your application are promptly reflected across all caching layers. This functionality is crucial for maintaining the freshness of your content, especially after making significant changes.

The process of clearing the CDN Cache and Edge Cache is integrated, meaning a single request will clear both caches if they are enabled. It can take two to five minutes to completely clear the cache across all data centers.

Clear cache activation

As with the CDN and Edge cache endpoints, you need an application ID to send this request. With the application ID in hand, You can send a POST request to /applications/${application_id}/clear-cache:

curl -i -X POST \
 'https://api.kinsta.com/v2/applications/{application_id}/clear-cache' \
 -H 'Authorization: Bearer '

Ensure you replace <YOUR_TOKEN_HERE> with your actual API key and {application_id} with the specific application ID.

Get started with Kinsta API today

You can do a lot with the Kinsta API, and the Kinsta team is actively adding new endpoints. Kristof Siket, our Development Team Lead for the Kinsta API, notes:

User feedback drives the prioritization of feature exposure. If you believe a specific tool or endpoint should be included in the Kinsta API, feel free to send in your feedback.

Check out previously published changelogs for the Kinsta API to understand what’s possible, how to get started, and the various permission levels and limits of the API:

• Introducing Kinsta API: The Power of Automation for Site Management
• Introducing New Kinsta API Endpoints: Environment CRUD, Edge Caching, Application Deployment
• New Kinsta API Endpoints: Clear CDN Cache and Push Environment
• New Kinsta API endpoints enhance WordPress site management

The post 3 new Kinsta API endpoints for Application Hosting (CDN, Edge Caching, & clear cache) appeared first on Kinsta®.

Company Owners and Company Administrators (the same user roles that have access to delete sites) can execute a reset that removes and reinstalls all WordPress files and the database but preserves any domain name configurations, backups, and activity logs.

Any standard and premium staging environments are also removed.

A reset reinstalls WordPress with the site details selected during the original launch of your site, including its data center and the addition of the multisite option, Yoast SEO, WooCommerce, and Easy Digital Downloads.

In addition to preserving your site’s historical backups, a site reset launches one more system backup before deleting the current installation.

Why reset a site when you can delete it?

The ultimate website do-over begins with the Delete Site option in MyKinsta. But a reset provides a clean slate for the WordPress installation without the loss of domain name configurations or historical data in backups and activity logs.

While a reset doesn’t allow you to change the site name displayed in MyKinsta, you can do that separately using the edit site name tool.

How to reset a WordPress site in MyKinsta

To reset a site, select it in the WordPress Sites list and then click on Info in the left-hand menu. Scroll down to click the Reset site button:

The next dialog asks you to provide a WordPress admin password for the new site. Other site details will reflect the options selected when the site was first created:

After clicking the Continue button, you will be asked to confirm your decision to reset the site by typing the site name and its environment indicator:

After confirming the reset, your site will be backed up before WordPress and its database are deleted and reinstalled.

If you change your mind after resetting a site, you can return your WordPress installation to a previous state by restoring a backup.

Get the most out of WordPress with Kinsta

A reset is a big step, but Kinsta offers many other ways to boost your website’s performance. From our easy-to-use tool for updating your site’s PHP version to our planet-wide CDN, edge caching, early hints, and image optimization, Kinsta’s Managed WordPress Hosting keeps your site running like it’s shiny and new.

The post Turn back time with the new reset option for WordPress sites appeared first on Kinsta®.