ServersRus in Trinidad and Tobago, WordPress and SLA

Who ServersRus may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

English for the offering, pricing and terms examined.

Control panel

ServersRus dashboard. Interface languages after login to confirm.

Support

Local team. Studio target of 12 hours, priority WhatsApp on Enterprise. Other languages to confirm.

ServersRus for WordPress in Trinidad and Tobago

ServersRus operates from Port of Spain and offers two paid plans with PHP, MySQL and WordPress installation. Local prices allow hosting to be budgeted in Trinidad and Tobago dollars. Choosing between Studio and Enterprise also affects resources, restore-point count and availability terms.

This profile follows a registration site that must distinguish a platform interruption from a problem specific to its form. The test uses a fictitious log and calculates counted downtime under explicit rules. It helps identify evidence to present to support and prepare incident tracking within the team.

Local-dollar prices, renewal and cancellation

The WordPress page and hosting terms agree on TTD amounts. The pricing page also displays USD references and an annual selector advertising two free months. Check the proposed total and currency before paying an annual cycle. The pricing page and terms specify local payments by card or supported debit method, with USD payment possible for customers outside the country. The company states that it currently does not charge VAT. Maintenance prices and any options should be handled separately.

The specific terms of November 4, 2026 describe prepaid service without automatic charging. Renewal requires payment for the next period. After expiry, sites remain active for seven days according to section 4, then may be put to sleep. General terms specify 30 days’ written notice for pricing changes and preserve the amount for the already paid period. Future pricing therefore depends on the rate applicable to the next subscription. If a contract is signed, its clauses prevail under section 1 of the hosting terms. The WordPress page’s 14-day commercial guarantee and section 5’s refusal to refund a started period deserve written confirmation before payment.

WordPress capacity and maintenance options

Studio and Enterprise support WordPress installation and have MySQL. The Creator plan at 69 TTD appears in the same comparison with an environment intended for HTML, CSS and JavaScript files. The table assigns it neither PHP, MySQL nor WordPress installation. The WordPress page describes a containerized environment with Apache and PHP 8.3. The table also mentions SSL and CDN delivery. For a site migration, ask for available PHP and MySQL versions, required modules and the file import procedure. Check cache rules for personalized pages, particularly logged-in accounts, booking and checkout.

The specific terms list a maximum upload of 5 GB on Studio and 15 GB on Enterprise. This limit appears alongside available space without explaining which screens or protocols apply the same rule. It is insufficient to determine allowed file size in the WordPress media library, which PHP or another component may limit. For a large site, confirm the migration mechanism and limits on database, process count and files. Site count is a commercial ceiling. Containers use shared infrastructure subject to a usage policy.

Hosting-only plans leave site update monitoring to the customer. The pricing page also presents assistance plans with a quantity of editorial interventions and different help turnaround times. Studio names both a technical plan and a maintenance plan based on it. To request WordPress management, specify expected tasks, plugins to maintain and how a change is validated. Staging appears among assistance services. Its availability within hosting alone should be checked for the project.

Languages, support and data location

The website, comparison and terms examined are in English. Dashboard languages after login and support languages remain to be confirmed. The WordPress offering locates the team in Port of Spain. Studio advertises priority support with a 12-hour target and Enterprise advertises a priority WhatsApp channel. A local team may be a factor if incidents are mainly detected during the site’s business hours in Trinidad and Tobago. Still ask when the clock starts, whether it means a first response and how nighttime or weekend requests are handled.

The proximity argument primarily concerns operations and billing. Cloudflare delivery concerns content access from different network locations. Neither the team address nor a CDN establishes the origin server or backup location. If location is a selection criterion, ask where the origin, database and restore points are hosted. Also prepare an example technical request for support, with domain, time and error type, without attaching payment data or registrant lists.

Backups, availability and incident tracking

Both plans provide on-demand backups. Studio lists 30 restore points and Enterprise 100. Section 9 of the hosting terms states that customers create points from the dashboard, the oldest is replaced when the limit is reached, and the host does not automatically back up sites. Deployment snapshots are also mentioned in the table. Ask whether they cover the WordPress database and files imported after deployment. For a registration site, create an independent copy before a change and ensure data arriving afterward can be reconciled or recovered.

The SLA and section 14 of the hosting terms give commitments of 99.9% for Studio and 99.95% for Enterprise. Section 3 of the SLA also presents a generic 99.9% target. For Enterprise, the applicability table and credit paragraph specify the 99.95% threshold. The SLA measures container reachability over a calendar month and excludes properly announced maintenance, application errors and certain external causes among other things. It requires reporting within seven days, with project, date, approximate time and observation. The host uses its own measurements, and any credit is applied to a later invoice.

A form can fail while the container continues responding. In the team’s log, separate form errors, observed slowness and no container response. Record test results with time and checked address. The same incident may be seen by several observers, which does not multiply its duration. If a status page announces maintenance, retain the announcement date and interval to facilitate comparison with support measurements.

AI and website creation

The WordPress page and feature overview document neither AI-generated WordPress pages nor an AI assistant included in Studio or Enterprise. Site design is offered separately through Telic. The hosting offering describes runtime environments and deployment tools. It details neither generative model quotas nor a service validating generated content. For use requiring a WordPress AI plugin, ask about plugin compatibility, resource needs and the cost of any external service.

For the example registration site, the priority is replaying the form without committing a real registration and finding events evidencing a failure. If the team considers an assistant to draft answers to frequently asked questions, use test text and have answers reviewed before publication. The form, content and maintenance access should remain usable if that external service is removed. Plan WordPress support terms and those of a possible AI provider concern separate services.

Local exercise: classify downtime

The fictitious log illustrates Studio and Enterprise thresholds. Support determines the measurements and eligibility of an actual incident. — Illustration by BlogPasCher.Open full-size illustration ↗

Objective. Replay classification of a fictitious 30-day month. The script uses one hour of announced maintenance, two overlapping observations of a platform-attributed incident, an application error and slowness with a reachable container. Each interval starts at the specified minute and excludes its ending minute. Announced maintenance is removed from the denominator. Accepted outage minutes are counted only once and subtracted from eligible minutes. Thresholds are tested on the unrounded result.

Run the command from the extracted ZIP directory with Node.js 18 or later and compare output with resultat-serversrus-trinite-tobago.json. The mixed scenario counts 28 minutes and gives 99.9351%. The additional overlap brings the total to 33 minutes and gives 99.9235%. An application error with a reachable container leaves the result at 100% in this model. In the mixed case, the calculation falls below Enterprise’s threshold and remains above Studio’s. In the final scenario, ten outage minutes are recorded, but five coincide with maintenance already excluded. The counted minutes therefore increase by only five.

To apply the method, date observations with their time zone, distinguish service from application and retain project availability evidence. If the cause is uncertain, the log should mark the incident as pending classification. The test covers the specified events and illustrates the published formula. It determines neither the cause of a real outage nor acceptance of a credit claim, which depends on the host’s terms and measurements.

node exercice-serversrus-trinite-tobago.cjs

Choose a plan and check recovery

Prepare a record bringing together two checks. The first opens a public container page and records its response. The second runs a registration journey with test data and records the confirmation message. If only registration fails, send details to the WordPress maintainer. If the container is inaccessible, attach the interval and time zone to the ticket. Keep evidence from both checks even if they concern the same incident.

Studio provides 25 GB storage, one vCPU, 1 GB memory and WordPress installation. It is the first plan in the comparison combining PHP and MySQL. For a registration site, check required plugins work with the PHP version and restoration recovers both files and recorded entries. Enterprise adds resources, a higher upload limit, more restore points and a higher availability target. Backup retention duration, location and restoration scope still need determination. Choosing this plan for its commitment also requires the team to know how to record and report incidents within the stated deadline.

Before payment, confirm amount, currency and cycle, then set a renewal reminder date. If the site depends on funding or payment approved by several people, schedule the reminder before expiry. Record in writing the treatment of the grace period, termination terms and the host’s response about the displayed 14 days. Expiry and free-offering sections use different wording in the hosting terms. For both paid plans, continuity should depend on payment for the next period or prepared recovery elsewhere. If the team signs a service contract, check that contract’s specific commitments before concluding on cancellation rights and possible fees.

After activation, create a restore point and separately try to retrieve an independent data copy. To prepare recovery, note items outside hosting, including the DNS zone and mail provider. Once the site is restored on an isolated copy, open the form and check where its data arrives. Whoever validates return to normal must know the last registration actually recovered. A plan offering 100 points still depends on how often those points are created and what they cover.

Finally, provide a simple log with tested address, time, symptom, estimated duration and name of the person contacting support. A reachable public page can coexist with a broken form. In that case, the functional incident must be addressed even if container availability calculation is unchanged. When an outage seems platform-related, send available observations to support within the required deadline and retain the request number. Test results serve as a model for checking overlapping observations and calculating duration. Support must still confirm the cause and accepted minutes.

For an outage observed near a month boundary, allocate minutes between the two calendar months used in the calculation. Also retain times allowing internal observations to align with platform measurements. The number of people affected and effect on registrations belong in team tracking. The SLA uses a service-time calculation, subject to its exclusions.

Prepare your site

• Invisible WordPress change: find and clear the right cache
• WordPress XML export and full backup: check what you can restore
• Contact Form 7 keeps loading after submission
• Download the availability calculation exercise