IRP for Cloud – Questions and Answers

IRP for Cloud is the ultimate network performance optimization service specifically designed to address inherent BGP routing deficiencies and eliminate scenarios when traffic is routed via slow or congested paths, taking cloud applications and websites performance to the next level.

The service leverages Noction’s proven Intelligent Routing Platform technology which measures critical network performance metrics such as latency and packet loss for various paths, analyses the collected information and automatically reroutes traffic through the best performing provider.

By sending traffic through the fastest available path, IRP for Cloud maximizes cloud network performance, offering lower packet loss than AWS for 78% of destinations and lower latency for 52% of destinations on average.

Connecting to the service is quite straightforward. You need to run a designated IRP for Cloud satellite VM, which can be found on your cloud provider’s marketplace. (Please note, the VM image is only available in those regions where the IRP for Cloud service is provided.)

In order to fully automate interconnection, including incident handling, the IRP for Cloud AMI requires an assigned IAM role. When it is created and assigned, the interconnection is established and there are no other changes to your AWS infrastructure.

Once deployed, the IRP for Cloud satellite VM runs entirely within your VPC and remains under your full control at all times.

Check out the setup guide for more details.

The IRP for Cloud satellite VM identifies your VPC on your behalf to IRP for Cloud service and obtains a Virtual Interface assignment. Once assigned it is activated and used by the IRP for Cloud service to forward packets to your VPC and validate that the VI is fully operational. At this stage the Virtual Interface can be used as an interface for traffic originated by your VPC resources. 

IRP for Cloud satellite VM adds two /1 routes pointing to the IRP for Cloud Virtual Interface that are preferred when compared to the /0 default route. The more specific routes present in the routing table override the IRP for Cloud /1 routes and allow you to segment what destination network segments use what gateway.

A series of specific cloud provider routes are added in order to ensure that your VPC communication with your cloud provider resources are still routed through your default gateway.

Once you run a designated IRP for Cloud satellite VM with traffic being routed through the shared IRP for Cloud Virtual Interface, you’ll receive a confirmation message from your cloud provider. In case of AWS, this is an automated email stating that a Direct Connect service is activated. Such emails are sent by cloud providers for notification purposes only. No action from your side is required.
When using IRP for Cloud, additional line items will be added to the normal invoice sent to you by your cloud provider:
– a Virtual Interface usage charge applied by your cloud provider
– an IRP for Cloud satellite VM usage charge that consists of
a) actual elastic instance charge applied by your cloud provider based on instance size and operating system and
b) instance usage charge applied through your cloud provider metering service.

That’s it. There’s no other administrative overhead for this.
How are we paid? The cloud provider charges you and we are then credited for your reported instance usage charge.

Navigate to cloud.noction.com. Use your cloud provider credentials to login. IRP for Cloud integrates with public cloud providers authentication services and you don’t need to create and maintain additional credentials.

Once logged into the IRP for Cloud dashboard at cloud.noction.com (check if your name as set with your cloud provider appears in the top right corner) you’ll be able to see the details regarding your personal VPC interconnection status, current usage and various other details.

In case there are other options you think would be useful to you and other clients, please let us know and we will add those for all our customers to use. 

You can use any monitoring system on your network.
At the same time, IRP for Cloud dashboard can offer the following important details on the IRP for Cloud service:
– your IRP for Cloud interconnect status
– your monthly usage
– the improvements IRP for Cloud service spotted compared to ordinary BGP and how many of those benefit your end users – the remote destinations you exchange information with
your overall and improved traffic shape.
IRP for Cloud satellite VM is a typical CentOS VM.
IRP for Cloud can take your AWS network performance to the next level and bring the following benefits:

  • higher conversion rates
  • faster load times
  • reduced VoIP jitter
  • faster content delivery
  • increased e-commerce revenue
  • better quality of video streaming
  • improved brand reputation and a lot more
Currently IRP for Cloud is available in Virginia (US-East 1) AWS region:
Reach out to us, if there is a specific region you would like us to cover. We can discuss your business needs individually.
In case the IRP for Cloud crashes, your traffic becomes rerouted through the default cloud providers routes. Thus the traffic starts flowing through the regular non-optimized paths.
IRP for Cloud pricing scales with consumption, just like the tariffs of your cloud provider do. Check out the IRP for Cloud tiered usage-based pricing model here.
For any technical support please contact us at support@noction.com describing the issues you encountered.
Even though we would hate to see you go and miss out on the cloud network optimization, you are always given the opportunity to cancel the service at any time.
The designed approach to stop using IRP for Cloud service is to stop/terminate the IRP for Cloud satellite VM. During this process the satellite VM will revert all the changes, specifically changes applied to your routing table and will release the IRP for Cloud shared Virtual Interface.