This is a beta/testing instance of PeeringDB. Some features may work differently than production. Do not store data here that you intend to keep - automatically scheduled refreshes from production are currently disabled.
Baffin Bay Networks
Organization
Also Known As
BBN
Long Name
Company Website
ASN
42649
IRR as-set/route-set
AS-BAFFIN
Route Server URL
Looking Glass URL
Network Type
NSP
IPv4 Prefixes
500
IPv6 Prefixes
50
Traffic Levels
Not Disclosed
Traffic Ratios
Not Disclosed
Geographic Scope
Global
Protocols Supported




Last Updated
2021-02-06T00:19:46Z
Public Peering Info Updated
2021-03-17T22:38:31
Peering Facility Info Updated
2020-04-15T13:41:10Z
Contact Info Updated
2019-01-21T11:50:25Z
Notes
Baffin Bay Networks is a Cybersecurity vendor with cloud-delivered Threat Protection, Threat Guidance and Threat Research.
--------------------------------------------------------------
We do require a up-to-date PeeringDB-entry to be eligible to peer with Baffin Bay Network.
We also do require that the peering-partner activates dualstack peering with both v4 and v6 peering.
--------------------------------------------------------------
Requests for setting up new peerings with Baffin Bay networks (here on after shorted as BBN) should be sent to peering@baffinbaynetworks.com. By setting up a peering with BBN, the peer is seen to have accepted this peering policy.
BBN is willing to enter into settlement-free peering with other Internet Service Providers (ISPs) under certain conditions:
The peering should be of mutual interest and benefit for BBN and the ISP.
Among the factors influencing BBN’s interest are the size of the ISP, the expected level and symmetry of the resulting traffic, the potential for reducing cost and improving performance etc.
BBN does not normally peer with customers of already existing peering partners.
Peering can be established on any of the public exchange points where BBN is present, or as a private network interconnect.
If the traffic on a private network interconnect reaches 70% of what a single interconnection can carry, both parties should immediately start planning for an upgrade of the connection.
If the traffic on a public exchange point reaches such a high level that it may impede other traffic, steps should be taken to move the traffic over to a private network interconnect.
The peering setup should be technically sound, and be in accordance with best practices.
Peering agreements are valid as long as neither party cancels the agreement.
BBN may without risk of financial or other penalty unilaterally decide to cancel a peering agreement if any of the conditions here are violated.
Peering Policy Information
Peering Policy
General Policy
Selective
Multiple Locations
Not Required
Ratio Requirement
No
Contract Requirement
Not Required
Contact Information
Role
Name
Visiblity
Phone
E-Mail
13688
Abuse
Abuse
Abuse
abuse@baffinbaynetworks.com
13688
NOC
NOC
NOC
noc@baffinbaynetworks.com
13688
Policy
Policy
Peering
peering@baffinbaynetworks.com
13688
Sales
Sales
Info
hello@baffinbaynetworks.com
13688
Sales
Sales
Sales
sales@baffinbaynetworks.com
Public Peering Exchange Points
Exchange
ASN
IPv4
IPv6
Speed
RS Peer
You may filter by Exchange, ASN or Speed.
Private Peering Facilities
Facility
ASN
Country
City
You may filter by Facility, ASN, Country or City.