4.6 April 2025

Release Notes

4.5 April 2025

1.3 - GA Release - March 2023

1.4 - Minor Release - April 2023

1.5 - Minor Release - May 2023

1.6 - Minor Release - Mid June 2023

1.7 - Minor Release - July(mid) - 2023

1.8 - Minor Release - August 2023

1.9 - Minor Release - August(end) 2023

2.0 - Minor Release - September 2023

2.10 - Minor Release - Mar 2024

2.1 - Minor Release - October 2023

2.2 - Minor Release - October(end)  2023

2.3 - Minor Release - November 2023

2.4- Minor Release - December 2023

2.5 - Minor Release - January 2024

2.6 - Minor Release - January(end) 2024

2.7 - Minor Release - February 2024

2.8 - Minor Release - March 2024

2.9 - Minor Release - March(end) 2024

3.0 June 2024

3.10 November 2024

3.11 December 2024

3.12 January 2024

3.13 January 2025

3.14 January 2025

3.1 June 2024

3.2 July 2024

3.3 Aug 2024

3.4 August 2024

3.5 September 2024

3.6 September 2024

3.7 October 2024

3.8 October 2024

3.9 November 2024

4.0 February 2025

4.1 February 2025

4.2 March 2025

4.3 - March 2025

4.4 March 2025

Activity Log

A - End

Amazon Web Services (AWS)

AWS Layer 3

Azure

Azure ExpressRoute

B - End

Billing

Change the Internet Rate Limit of a Virtual Appliance

Cisco Catalyst 8000V Edge Software

Cloud to Cloud Connection

Complete Organization Profile

Complete Your Profile

Create A Billing Profile

Create a Cisco Catalyst 8000V Virtual Appliance on Polarin

Create a Link Aggregation Group

Create a Polarin Account

Create a Port

Create a Virtual Connection

Create A Virtual Connection

Create a Virtual Router

Data Center Locations

Datacenter to Cloud Connection

Datacenter to Datacenter Connection

Delete Virtual Connection

Different types of Virtual Connections to a Virtual Appliance

FAQs

Google Cloud

Google Cloud- Layer 3

Invite Team Members to Polarin

Layer 2 - Port

Layer 3 - Virtual Router

List of Polarin Network Edge (PNE) PoPs

List of Supported KYC Documents

Oracle FastConnect

Oracle FastConnect - Layer 3

Overview

Port Metrics

Reserved Plan Pricing

Service Chaining (Connecting two Virtual Appliances)

Subscriptions

Tagged Virtual Connection

Two-Factor Authentication (2FA)

Understand Port Status

Understand Virtual Connection Status

Understand Virtual Router Status

Untagged Virtual Connection

Update a Virtual Connection

Update Password

User Management

<html>
<head>
 <title>
 Billing
 </title>
</head>
<body>
 
 This section provides an explanation of the billing process for Polarin services, including the billing activation date, billing from entity, billing to locations, and general guidelines.<h2 id="Billing-BillingInformationforPolarinServices">Billing Information for Polarin Services</h2>The billing from and to addresses will be determined by the services you choose. For more information, refer to <a href="https://lightstorm.atlassian.net/wiki/spaces/Polarin/pages/edit-v2/137560107#Table-1---Billing-Information-for-Services" rel="nofollow">Table 1 - Billing Information for Services</a>.<h3 style="text-align: center;" id="Billing-Table1-BillingInformationforServices">Table 1 - Billing Information for Services</h3><div class="table-wrap"><table data-layout="wide" data-local-id="ab9a39ea-0a82-4445-a95e-28e975edf5ce" class="confluenceTable"><colgroup><col style="width: 71.0px;"><col style="width: 122.0px;"><col style="width: 300.0px;"><col style="width: 467.0px;"></colgroup><tbody><tr><th class="confluenceTh">SL No.</th><th class="confluenceTh">Services</th><th class="confluenceTh">Lightstorm Entity (Bill From)</th><th class="confluenceTh">Billing To</th></tr><tr><td class="confluenceTd">1</td><td class="confluenceTd">Port</td><td class="confluenceTd">Lightstorm Datacenters Private Limited (LDC) - Maharashtra</td><td class="confluenceTd">We are billing to the customer’s location, which is provided by the customer when they place an order.For example: Scenario 1: If XYZ Private Limited orders a port and chooses the billing address to be the Navi Mumbai location, the billing information would be as follows:<ul><li>Billing From - Lightstorm Datacenters Private Limited, Maharashtra</li><li>Billing To - XYZ Private Limited, Navi Mumbai, Maharashtra</li></ul>Scenario 2: If ABC Private Limited orders a port and chooses the billing address to be the Chennai location, the billing information would be as follows:<ul><li>Billing From - Lightstorm Datacenters Private Limited, Maharashtra</li><li>Billing To - ABC Private Limited, Chennai, Tamil Nadu</li></ul></td></tr><tr><td class="confluenceTd">2</td><td class="confluenceTd">DC - DC Connection </td><td class="confluenceTd">Lightstorm Telecom Connectivity Private Limited (LTC)<div class="confluence-information-macro confluence-information-macro-information"><div class="confluence-information-macro-body">Note: <ol start="1"><li>The billing from the state will be determined by the location of the A-End and B-End data centers. If these locations are in the same state, the billing will be generated from that state.</li><li> If the locations are in different states, two bills will be generated with equal prices, and each bill will be generated from the state where the respective data center is located.</li></ol></div></div></td><td class="confluenceTd">We are billing to the customer’s location, which is provided by the customer when they place an order.For example: Scenario 1: If XYZ Private Limited places a connection between Mumbai DC (A-End) and Pune DC (B-End), and chooses the billing address to be the Pune location, the billing information would be as follows:<ul><li>Billing From - Lightstorm Telecom Connectivity Private Limited, Mumbai, Maharashtra</li><li>Billing To - XYZ Private Limited, Pune, Maharashtra</li></ul>Scenario 2: If ABC Private Limited places a connection between Bengaluru DC (A-End) and Noida DC (B-End), and chooses the billing address to be the Noida location, the billing information would be as follows:Invoice 1:<ul><li>Billing From - Lightstorm Datacenters Private Limited, Bengaluru, Karnataka (50% of the total price)</li><li>Billing To - ABC Private Limited, Noida, Uttar Pradesh</li></ul>Invoice 2:<ul><li>Billing From - Lightstorm Datacenters Private Limited, Noida, Uttar Pradesh (50% of the total price)</li><li>Billing To - ABC Private Limited, Noida, Uttar Pradesh</li></ul></td></tr><tr><td class="confluenceTd">3</td><td class="confluenceTd">DC - Cloud Connection</td><td class="confluenceTd">Lightstorm Datacenters Private Limited (LDC) - Maharashtra </td><td class="confluenceTd">We are billing to the customer’s location, which is provided by the customer when they place an order.</td></tr><tr><td class="confluenceTd">4</td><td class="confluenceTd">Cloud - Cloud Connection</td><td class="confluenceTd">Lightstorm Datacenters Private Limited (LDC) - Maharashtra</td><td class="confluenceTd">We are billing to the customer’s location, which is provided by the customer when they place an order.</td></tr><tr><td class="confluenceTd">5</td><td class="confluenceTd">Virtual Router</td><td class="confluenceTd">Lightstorm Datacenters Private Limited (LDC) - Maharashtra</td><td class="confluenceTd">We are billing to the customer’s location, which is provided by the customer when they place an order.</td></tr></tbody></table></div><h2 id="Billing-ServiceActivation">Service Activation</h2>The general guidelines of service activation:<ul><li>The billing activation date may vary depending on the services you choose. For more information on service activation, refer to <a href="https://lightstorm.atlassian.net/wiki/spaces/Polarin/pages/edit-v2/137560107#Table-2---Service-Activation" rel="nofollow">Table 2 - Service Activation</a>.</li><li>All invoices are generated on the 1st of every month. For example, if a customer orders the DC-Cloud virtual connection on January 12th, 2022 and the port goes live on January 16th, 2022, they will receive their first invoice on January 16th, 2022. After that, they will receive invoices on the 1st of every month.</li><li>All invoices must be paid within 30-days.</li></ul><h3 style="text-align: center;" id="Billing-Table2-ServiceActivation">Table 2 - Service Activation</h3><div class="table-wrap"><table data-layout="default" data-local-id="e6eecbb1-c648-4e91-b96b-7837ed3b4178" class="confluenceTable"><colgroup><col style="width: 69.0px;"><col style="width: 215.0px;"><col style="width: 476.0px;"></colgroup><tbody><tr><th class="confluenceTh">SL No.</th><th class="confluenceTh">Services</th><th class="confluenceTh">Billing Activation Date</th></tr><tr><td class="confluenceTd">1</td><td class="confluenceTd">Port</td><td class="confluenceTd">The billing will start from whichever date is earlier:<ul><li>30 calendar days from the Port creation date or</li><li>Port live date</li></ul></td></tr><tr><td class="confluenceTd">2</td><td class="confluenceTd">DC - DC Connection </td><td class="confluenceTd">The billing will start from:<ul><li>The connection created date, if both ports are live.</li><li>The second port live date, if one port is live.</li><li>The date when both ports are live, if no port is live.</li></ul></td></tr><tr><td class="confluenceTd">3</td><td class="confluenceTd">DC - Cloud Connection</td><td class="confluenceTd">The billing will start from:<ul><li>The date of connection creation, if the port is live.</li><li>The date when the port is live.</li></ul></td></tr><tr><td class="confluenceTd">4</td><td class="confluenceTd">Cloud - Cloud Connection</td><td class="confluenceTd">The billing will start from:<ul><li>The connection created date, if the port is live.</li><li>The date when the port is live.</li></ul></td></tr><tr><td class="confluenceTd">5</td><td class="confluenceTd">Virtual Router</td><td class="confluenceTd">The billing will start from the date of connection creation.</td></tr></tbody></table></div>
 
</body>
</html>