Performance and availability standards for InEvent custom landing pages

This article outlines the performance standards and availability guarantees for InEvent custom landing pages. It covers key topics such as expected uptime and downtime, bandwidth capacity for handling concurrent users, and the platform's ability to support large files without compromising stability or load speed.

What is the expected uptime and downtime for InEvent custom landing pages?

InEvent guarantees a minimum uptime of 99.9% for its platform, including custom landing pages, as part of its standard Service Level Agreement (SLA). Downtime excludes scheduled maintenance, which is communicated in advance to ensure minimal disruption. Real-time performance metrics, including uptime, are available on the InEvent Trust page, which provides information on system availability.

What is the bandwidth and throughput capacity for handling concurrent users?

InEvent’s platform is designed to handle high-traffic scenarios, supporting thousands of concurrent users on custom landing pages, depending on the configuration and hosting plan. The infrastructure leverages scalable cloud resources to ensure consistent performance during peak usage. While specific throughput metrics depend on the deployment, InEvent’s architecture is optimized to maintain page load times under 2 seconds for standard configurations, even under significant concurrent user loads. See our Frequently asked RFP questions and Technical requirements: Troubleshooting guide articles for more information.

Will including large files, such as a 20MB high-quality image, cause buffering when loading InEvent custom landing pages?

InEvent’s platform supports uploading various file types, including high‑quality images of 20 MB or more, without noticeable buffering under normal conditions. It leverages optimized Content Delivery Networks (CDNs), image compression, lazy loading, and caching to keep load times fast, typically under 2 seconds for standard landing pages. While the infrastructure is built to handle large files, actual performance may vary depending on factors like image format, user internet speed, and device specifications.