-
Notifications
You must be signed in to change notification settings - Fork 0
/
feed.xml
447 lines (447 loc) · 60.7 KB
/
feed.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title>Emerald Onion</title>
<subtitle>Building public-use privacy infrastructure centered on human rights since 2017.</subtitle>
<link href="https://emeraldonion.org/feed.xml" rel="self" type="application/atom+xml"/>
<link href="https://emeraldonion.org"/>
<updated>2024-09-05T00:00:00+00:00</updated>
<id>https://emeraldonion.org/feed.xml</id>
<entry xml:lang="en">
<title>Guide to Starting a Human Rights ISP</title>
<published>2024-09-05T00:00:00+00:00</published>
<updated>2024-09-05T00:00:00+00:00</updated>
<link href="https://emeraldonion.org/blog/starting-a-human-rights-isp/" type="text/html"/>
<id>https://emeraldonion.org/blog/starting-a-human-rights-isp/</id>
<content type="html"><h1 id="introduction">Introduction<a class="zola-anchor" href="#introduction" aria-label="Anchor link for: introduction">#</a></h1>
<p>This article was originally published on emeraldonion.org in 2017 and has been revamped in 2024. In addition, in 2018, yawnbox <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.youtube.com/watch?v=cs6a1i4Owic">spoke at DEF CON 26</a> (YouTube link) about creating Emerald Onion. Please be aware that because Emerald Onion is a US-based not-for-profit, this guide is centered on US laws and programs. To date, we are aware of at least four human rights ISPs that have formed in part because of Emerald Onion's example. We are always excited to provide guidance to those interested. But we are not the first nonprofit to do this in the US! Our inspiration was <a rel="noopener nofollow noreferrer" target="_blank" href="https://riseup.net">RiseUp</a> and <a rel="noopener nofollow noreferrer" target="_blank" href="https://calyxinstitute.org">The Calyx Institute</a>.</p>
<p>Part of Emerald Onion’s mission is to share our actions in detail in order to help educate others who wish to create their own human-rights focused transit internet service provider. We have a vision that entails many trusted nonprofits setting up and operating long-term, stable, and fast Tor routing operations. Below you will find a robust overview of tasks performed to create Emerald Onion.</p>
<h1 id="the-steps-we-took-to-create-emerald-onion">The steps we took to create Emerald Onion<a class="zola-anchor" href="#the-steps-we-took-to-create-emerald-onion" aria-label="Anchor link for: the-steps-we-took-to-create-emerald-onion">#</a></h1>
<h2 id="founding">Founding<a class="zola-anchor" href="#founding" aria-label="Anchor link for: founding">#</a></h2>
<ol>
<li>
<p>Invite meaningful and trusted people for the board of directors, executive leadership, and advisory board.</p>
</li>
<li>
<p>Create a mission and vision statements, and organizational goals.</p>
</li>
<li>
<p>Setup a password manager for generating and documenting organizational passwords.</p>
</li>
<li>
<p>Purchase a domain name, setup the website, and setup social media accounts.</p>
</li>
<li>
<p>Setup Microsoft hosted email service for admin@ and abuse@ inboxes. Once you become a 501(c)3, Microsoft provides <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.microsoft.com/en-us/microsoft-365/enterprise/nonprofit-plans-and-pricing">free enterprise services</a> for not-for-profits.</p>
<p>2024 note: After much research, we found that Google email does not allow domain admins to have access to admin@ and abuse@ email addresses. We presume because Google wants to be able to perform their own conotrols over what comes into these email addresses. It's critical for Tor relay operators to have access to these email addresses, and use them to their fullest extent. If you're up to the challenge, self-hosted email can work great (with proper SPF, DMARC, DKIM, and DNSSEC/DANE configurations) with open source solutions such as <a rel="noopener nofollow noreferrer" target="_blank" href="https://mailcow.email">MailCow</a>.</p>
</li>
<li>
<p>Setup a UPS Store mailbox for registration (your primary “place of business” address) and find Registered Agent services for your registered agent. A legitimate Registered Agent is required in the State of Washington.</p>
<p>2024 note: Since 2024, and since more than one of our Board of Director members lives abroad, we've since moved to <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.legalzoom.com/business/business-operations/lz-virtual-mail-overview.html">Legal Zoom's mail scanning service</a> so we can be responsive to US government legal demands that get send my mail.</p>
</li>
<li>
<p>Establish <a rel="noopener nofollow noreferrer" target="_blank" href="https://github.com/emeraldonion/emeraldonion.github.io/blob/master/files/EO_Articles_Of_Incorporation.pdf">Articles of Incorporation</a>. Our articles were drafted with the help of our attorney, and they merge both (at the time) Washington state requirements and IRS requirements.</p>
</li>
<li>
<p>Apply for Washington State nonprofit status. Be sure to use your Registered Agents and also your mail receiving or mail forwarding service as your "place of business", unless of course you have a physical office somewhere.</p>
<p>2024 note: Even before this step, but certainly after, be sure to conduct B2B communications with your business email and phone number.</p>
</li>
<li>
<p>Begin contacting local data center service providers and upstream internet service providers that offer their services in said data center.</p>
<p>2024 notes:</p>
<ul>
<li>
<p>Picking up "the language" of data centers and internet service providers has its own learning curve.</p>
<ol>
<li>You need data center co-location: a place to rack your servers and network gear. Colo service requests include but are not limited to, the amount of physical "U space" that you need for your servers, like a half-rack, quarter-rack, or shared space. We disadvise shared rack space because Tor relays should be behind lock and key. Colo requests also need to know how much power in amps you expect to need.</li>
<li>You need IP transit, which is your organization's general internet access. Some colo providers offer their own "mixed network" transit, which means they blend multiple Tier-1 ISPs together to offer cheaper transit. Otherwise, you need to seek out Tier-1 or Tier-2 transit ISPs, and the cheaper the better. Tor relays can saturate bandwidth easily, so it may be important to seek "unmetered" or "fully commited" 1Gbps or 10Gbps ports. Otherwise, "95th percentile" 10Gbps will be cheaper and allow you to burst up to 10Gbps. Getting your own IP transit, in other words not provided by the colo provider, may require "cross connects", which usually cost money. A cross-connect is simply the service of the data center seting up then maintaining the physical copper or fiber connection from your rack to your upstream ISP.</li>
<li>You may need, and should seek out, access to <a rel="noopener nofollow noreferrer" target="_blank" href="https://emeraldonion.org/blog/internet-exchange-points-in-the-united-states/">Internet Exchange Points</a> (IXP). Expect cross-connects to IXPs, but some colo providers may provide free cross-connects to local IXPs, be sure to ask about free or reduced cross-connects.</li>
</ol>
</li>
<li>
<p>Again and again, we found that data centers and transit ISPs have extremely little empathy for not-for-profits like Emerald Onion. They do not care that we are 100% volunteer run and 100% donation-based. They certainly don't care about Tor when you are bringing your own ASN and IP space. The internet infrastructure ecosystem is for-profit, so don't get discouraged with your kind requests are not supported.</p>
</li>
<li>
<p>To date, we've found that Huricane Electric's <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.he.net/tour/fremont2.html">FMT2 datacenter</a> is the cheapest unmetered 10Gbps transit that we can find. We have also found many regional co-ops exist, but rarely do they support 10Gbps transit, or more. Most critically, it's important to find solutions that minimize recurring fees. One-time setup fees, for things like cross-connects, are the kinds of things to ask for, or kindly request to waive or reduce recurring costs.</p>
</li>
<li>
<p>Are you going to have your own BGP-capable edge router? and will you announce your own ASN and IP space to the rest of the internet? If not, and you want your upsteam ISP to do this for you, then you need to be clear about this in your service request. You'll need to ask them for a <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.cidr.eu/en/letter-of-authorization">Letter of Authorization</a>.</p>
</li>
<li>
<p>Be mindful about the opportunities that <a rel="noopener nofollow noreferrer" target="_blank" href="https://emeraldonion.org/blog/internet-exchange-points-in-the-united-states/">IXPs provide</a>.</p>
</li>
</ul>
</li>
<li>
<p>Apply for <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin">Employer Identification Number</a> (EIN/TIN) from IRS, even without paid employees.</p>
</li>
<li>
<p>Apply for a business bank account with a local nonprofit credit union and obtain debit cards. In the US, a state nonprofit corporation only needs to provide the business name, contact information, the EIN, and the state registration of the corporation that shows the Unified Business Identifier (UBI).</p>
</li>
<li>
<p>Apply to the IRS for 501(c)(3) status using the <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.irs.gov/forms-pubs/about-form-1023-ez">1023-EZ</a>.</p>
<p>2024 note: See <a rel="noopener nofollow noreferrer" target="_blank" href="https://github.com/emeraldonion/emeraldonion.github.io/blob/master/files/EO_IRS_1023EZ.pdf">our 2017 1023-EZ</a>. The 1023-EZ route is prudent for small nonprofits. As long as you plan on making less than $50,000 a year, which we have done every single year, this is the quickest and easiest path to 501(c)(3) public charity status. A lawyer is not needed! From then on, every year, the only tax filing that is required at the IRS level is the <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.irs.gov/charities-non-profits/annual-electronic-notice-form-990-n-for-small-organizations-faqs-how-to-file">990-N postcard</a>, simply attesting to the fact that Emerald Onion has not made more than $50,000 in the taxable year. It's very manageable for small volunteer group.</p>
</li>
</ol>
<h2 id="establishing">Establishing<a class="zola-anchor" href="#establishing" aria-label="Anchor link for: establishing">#</a></h2>
<ol start="13">
<li>
<p>Once your Charity status has been granted by the IRS, sign up the org for <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.paypal.com/us/non-profit/fundraising/fundraising-online">PayPal’s Nonprofit services</a>.</p>
<p>2024 note: Paypal has been instrumental for us to receive funding. Both direct from people, but also to fasciliate corporate donations. Paypal waives all fees for 501(c)(3) not-for-profits, meaning we get 100% of a person's donation. One weird potentially odd thing about this setup is that Paypal's not-for-profit org is the entity that people give a donation to, and that org simply forwards 100% of the donation to Emerald Onion. To donation/tax receipts will appear to be Paypal.</p>
</li>
<li>
<p>Apply for nonprofit startup grants when available.</p>
<p>2024 note: We were very fortunate to be provided a $5,000 startup grant by the then TorServers.net. We would not have been able to launch without this initial funding.</p>
</li>
<li>
<p>Setup a phone call with chosen legal representation to discuss optional support. <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.eff.org/about/contact">The EFF</a> may be an option. If seeking private practice, request a quote to create a general legal FAQ and abuse response templates for managing complaints from our upstream ISP and direct complaints. Feel free to start with our free <a rel="noopener nofollow noreferrer" target="_blank" href="https://emeraldonion.org/legal/">Legal FAQ</a>. If needing paid legal support, request a “Form Engagement Letter” from legal representation.</p>
<p>2024 note: Our Legal FAQ has been a foundational element for our sustained legal safety. We use this exact template in our email autoresponses via ZenDesk, and anytime we are emailed by government law enforcement officials, we link them to our public Legal FAQ.</p>
</li>
<li>
<p>Deposit enough funds into the business bank account. This may include: several months of business insurance, data center services including IP transit services, legal services, all RIR (like ARIN) registration and IP allocation costs, and hardware costs.</p>
</li>
<li>
<p>Purchase computer and networking parts for a Tor router and edge router.</p>
</li>
<li>
<p>Setup a <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.zendesk.com/register/">Zendesk free trial</a> for testing, tracking, and responding to abuse@ communications, and set up automated responses with the Legal FAQ.</p>
</li>
<li>
<p>Create <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.arin.net/resources/guide/account/records/poc/">ARIN POC records</a> for your organization, which will also depend on personal records.</p>
<p>2024 note: When setting up POC records, be very sure to use the businesses's receiving/forwarding mail service address. We did not use our Registered Agent address with our POC records since we want to minimize who has access to government legal demands.</p>
</li>
<li>
<p>Setup insurance provider(s) needed for data center co-location service, including “commercial general liability”, “business property protection”, and “professional liability” insurance.</p>
<p>2024 note: We use <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.thehartford.com/business-insurance-landing-page">The Hardtford</a>, and have since day one.</p>
</li>
<li>
<p>Finalize negotiating all fees with your data center and IP transit service (upstream ISP) providers and then sign contracts. The transit provider needs to perform an <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.arin.net/vault/blog/2018/05/03/which-swip-type-is-right-for-you/">IP SWIP</a> for updating ARIN’s WHOIS so that your organization is on record for using leased IP space. Once you have your upstream ISP-provided IP addresses, now you can apply for your own ASN and your own IP space.</p>
</li>
<li>
<p><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.arin.net/resources/guide/request/">Apply to ARIN</a> (or your RIR) for your organization's <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.arin.net/resources/guide/asn/">Autonomous Systems Number</a> (ASN) and then an /48 or /32 IPv6 block. It's important to get IP space in this order. Understand <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.arin.net/participate/policy/nrpm/#4-10-dedicated-ipv4-allocation-to-facilitate-ipv6-deployment">ARIN's 4.10 rule</a> for obtaining a free /24 IPv4 block. Once you have obtained an ASN and IPv6 block, apply for a free /24 IPv4 block using ARIN's 4.10 rule.</p>
<p>2024 note: Emerald Onion pays an annual fee of $250 for our ASN and $250 for our /48 IPv6 block. Back in 2017, we applied for our first 4.10 IPv4 block with success by explaining how Tor needs more IPv6 relays in order to eventually allow IPv6-only relays. So in order to facilitate more IPv6 in the Tor network, operators such as Emerald Onion needs "immediate" access to an IPv4 block. A few years later, since Emerald Onion now has multiple POPs, we successfully obtained a second /24 IPv4 block using the same 4.10 rule. So, our IPv4 blocks are free and perpetual.</p>
<ul>
<li>Example: our <a rel="noopener nofollow noreferrer" target="_blank" href="https://github.com/emeraldonion/emeraldonion.github.io/blob/master/images/ARIN-ASN-Request.png">ASN request</a></li>
<li>Example: our <a rel="noopener nofollow noreferrer" target="_blank" href="https://github.com/emeraldonion/emeraldonion.github.io/blob/master/images/ARIN-IPv6-request.png">IPv6 request</a></li>
<li>Example: our <a rel="noopener nofollow noreferrer" target="_blank" href="https://github.com/emeraldonion/emeraldonion.github.io/blob/master/images/ARIN-IPv4-Request.png">IPv4 request</a></li>
</ul>
</li>
</ol>
<h2 id="deploying">Deploying<a class="zola-anchor" href="#deploying" aria-label="Anchor link for: deploying">#</a></h2>
<ol start="23">
<li>
<p>Publish a <a rel="noopener nofollow noreferrer" target="_blank" href="https://emeraldonion.org/donate/">donation page</a>, legal FAQ, mission, and vision statements on the website.</p>
</li>
<li>
<p>Deploy your gear in your new data center. Only run Tor bridges or Tor middle relays until securing and configuring RIR-provisioned IP scopes so that you don't cause a legal headache for your transit provider.</p>
<p>2024 note: When configuring operating systems and applications, be sure to minimize or avoid any network logging, and be transparent about that on your published Legal FAQ. Never operate out-of-scope of your Legal FAQ.</p>
</li>
<li>
<p>Actively publish work performed on social media and the blog. We recommend Mastodon!</p>
</li>
</ol>
</content>
</entry>
<entry xml:lang="en">
<title>Internet Exchange Points in the United States</title>
<published>2017-08-13T00:00:00+00:00</published>
<updated>2017-08-13T00:00:00+00:00</updated>
<link href="https://emeraldonion.org/blog/internet-exchange-points-in-the-united-states/" type="text/html"/>
<id>https://emeraldonion.org/blog/internet-exchange-points-in-the-united-states/</id>
<content type="html"><h1 id="internet-exchange-points-in-the-united-states">Internet Exchange Points in the United States<a class="zola-anchor" href="#internet-exchange-points-in-the-united-states" aria-label="Anchor link for: internet-exchange-points-in-the-united-states">#</a></h1>
<p>Emerald Onion is researching IXPs in the U.S.A. in order to identify areas of priority as it concerns increasing global Tor network capacity by way of putting Tor routers directly on these highly interconnected networks. Putting Tor exit routers in IXPs, for example, may reduce network latency to end points. It may also reduce network hops, potentially minimizing the possibility of third-party surveillance. Emerald Onion envisions a future where the Tor network is composed of much larger and more stable network operators, globally.</p>
<h2 id="questions">Questions<a class="zola-anchor" href="#questions" aria-label="Anchor link for: questions">#</a></h2>
<ol>
<li>Are there any Tor routers connected to any United States-based IXPs? If so, which ones and who operates them?</li>
<li>Is this IXP friendly to Tor?</li>
<li>What is the organizational structure of this IXP? Such as corporate-run or community-driven, etc.</li>
<li>What qualities of an IXP should impact how meaningful it would be for the Tor network?</li>
</ol>
<ul>
<li>Number of participants?</li>
<li>Access to specific participants?</li>
<li>Nonprofit?</li>
<li>Community driven?</li>
<li>Affordability?</li>
<li>Geolocation?</li>
<li>Prohibits network surveillance?</li>
</ul>
<h2 id="a-top-20-list-of-cities-to-focus-on-for-tor-development">A top 20 list of cities to focus on for Tor development?<a class="zola-anchor" href="#a-top-20-list-of-cities-to-focus-on-for-tor-development" aria-label="Anchor link for: a-top-20-list-of-cities-to-focus-on-for-tor-development">#</a></h2>
<ol>
<li>Chicago, IL has at least 12 IXPs</li>
<li>New York City, NY has at least 9 IXPs (and has <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/net/4594">Calyx Institute</a>)</li>
<li>Dallas, TX has at least 6 IXPs</li>
<li>Los Angeles, CA has at least 6 IXPs</li>
<li>Miami, FL has at least 6 IXPs</li>
<li>Seattle, WA has at least 5 IXPs (and has <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/net/9021">Riseup</a> and <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/net/14010">Emerald Onion</a>)</li>
<li>San Jose, CA has at least 5 IXPs</li>
<li>Phoenix, AZ has at least 5 IXPs</li>
<li>Ashburn, VA has at least 3 IXPs</li>
<li>Reston, VA has at least 3 IXPs</li>
<li>Boston, MA has at least 3 IXPs</li>
<li>Atlanta, GA has at least 3 IXPs</li>
<li>Portland, OR has at least 3 IXPs</li>
<li>Honolulu, HI has at least 2 IXPs</li>
<li>Denver, CO has at least 2 IXPs</li>
<li>Vienna, VA has at least 2 IXPs</li>
<li>Palo Alto, CA has at least 1 IXP</li>
<li>Salt Lake City, UT has at least 1 IXP (and has <a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/net/789">XMission</a>)</li>
<li>Minneapolis, MN has at least 1 IXP</li>
<li>Detroit, MI has at least 1 IXP</li>
</ol>
<h2 id="ixps-in-the-united-states">IXPs in the United States<a class="zola-anchor" href="#ixps-in-the-united-states" aria-label="Anchor link for: ixps-in-the-united-states">#</a></h2>
<h3 id="ashburn-va">Ashburn, VA<a class="zola-anchor" href="#ashburn-va" aria-label="Anchor link for: ashburn-va">#</a></h3>
<ol>
<li>Equinix Ashburn Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1">Equinix Ashburn</a>)</li>
<li>LINX Northern Virginia (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/777">LINX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/15">MAE East</a></li>
</ol>
<h3 id="ashland-va">Ashland, VA<a class="zola-anchor" href="#ashland-va" aria-label="Anchor link for: ashland-va">#</a></h3>
<ol>
<li>Richmond Virginia Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1002">RVA-IX</a>)</li>
</ol>
<h3 id="atlanta-ga">Atlanta, GA<a class="zola-anchor" href="#atlanta-ga" aria-label="Anchor link for: atlanta-ga">#</a></h3>
<ol>
<li>Digital Realty / Telx Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/22">TIE</a>)</li>
<li>Equinix Internet Exchange Atlanta (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/9">Equinix Atlanta</a>)</li>
<li>Southeast Network Access Point (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/627">SNAP</a>)</li>
</ol>
<h3 id="austin-tx">Austin, TX<a class="zola-anchor" href="#austin-tx" aria-label="Anchor link for: austin-tx">#</a></h3>
<ol>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/674">CyrusOne IX</a>)</li>
</ol>
<h3 id="billings-mt">Billings, MT<a class="zola-anchor" href="#billings-mt" aria-label="Anchor link for: billings-mt">#</a></h3>
<ol>
<li>Yellowstone Regional Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/199">YRIX</a>)</li>
</ol>
<h3 id="boston-ma">Boston, MA<a class="zola-anchor" href="#boston-ma" aria-label="Anchor link for: boston-ma">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/565">Boston Internet Exchange</a></li>
<li>Massachusetts eXchange Point (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/25">MXP</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/333">CoreSite - Any2 Boston</a></li>
</ol>
<h3 id="buffalo-ny">Buffalo, NY<a class="zola-anchor" href="#buffalo-ny" aria-label="Anchor link for: buffalo-ny">#</a></h3>
<ol>
<li>Buffalo Niagara International Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/496">BNIIX</a>)</li>
</ol>
<h3 id="chicago-il">Chicago, IL<a class="zola-anchor" href="#chicago-il" aria-label="Anchor link for: chicago-il">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/944">AMS-IX Chicago</a></li>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1142">CyrusOne IX</a>)</li>
<li>Equinix Chicago Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/2">Equinix Chicago</a>)</li>
<li>Greater Chicago International Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/640">GCIIX</a>)</li>
<li>United IX - Chicago (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/239">ChIX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/226">CoreSite - Any2 Chicago</a></li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/20">MAE Central</a></li>
</ol>
<h3 id="columbus-oh">Columbus, OH<a class="zola-anchor" href="#columbus-oh" aria-label="Anchor link for: columbus-oh">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/869">OhioIX</a></li>
</ol>
<h3 id="dallas-tx">Dallas, TX<a class="zola-anchor" href="#dallas-tx" aria-label="Anchor link for: dallas-tx">#</a></h3>
<ol>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/672">CyrusOne IX</a>)</li>
<li>DE-CIX, the Dallas Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1249">DE-CIX Dallas</a>)</li>
<li>Digital Realty / Telx Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/322">TIE</a>)</li>
<li>Equinix Dallas Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/3">Equinix Dallas</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/20">MAE Central</a></li>
<li>Megaport MegaIX Dallas (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1180">MegaIX Dallas</a>)</li>
</ol>
<h3 id="denver-co">Denver, CO<a class="zola-anchor" href="#denver-co" aria-label="Anchor link for: denver-co">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/254">CoreSite - Any2 Denver</a></li>
<li>Interconnection eXchange Denver (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1207">IX-Denver</a>)</li>
</ol>
<h3 id="detroit-mi">Detroit, MI<a class="zola-anchor" href="#detroit-mi" aria-label="Anchor link for: detroit-mi">#</a></h3>
<ol>
<li>Detroit Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1006">DET-IX</a>)</li>
</ol>
<h3 id="duluth-nm">Duluth, NM<a class="zola-anchor" href="#duluth-nm" aria-label="Anchor link for: duluth-nm">#</a></h3>
<ol>
<li>Twin Ports Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/624">TP-IX</a>)</li>
</ol>
<h3 id="gillette-wy">Gillette, WY<a class="zola-anchor" href="#gillette-wy" aria-label="Anchor link for: gillette-wy">#</a></h3>
<ol>
<li>BigHorn Fiber Internet Exchang (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/791">BFIX</a>)</li>
</ol>
<h3 id="hagatna-guam">Hagåtña, Guam<a class="zola-anchor" href="#hagatna-guam" aria-label="Anchor link for: hagatna-guam">#</a></h3>
<ol>
<li>Guam Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/463">GU-IX</a>)</li>
</ol>
<h3 id="honolulu-hi">Honolulu, HI<a class="zola-anchor" href="#honolulu-hi" aria-label="Anchor link for: honolulu-hi">#</a></h3>
<ol>
<li>DRFortress Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/267">DRF IX</a>)</li>
<li>Hawaii Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/189">HIX</a>)</li>
</ol>
<h3 id="houston-tx">Houston, TX<a class="zola-anchor" href="#houston-tx" aria-label="Anchor link for: houston-tx">#</a></h3>
<ol>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/673">CyrusOne IX</a>)</li>
</ol>
<h3 id="indianapolis-in">Indianapolis, IN<a class="zola-anchor" href="#indianapolis-in" aria-label="Anchor link for: indianapolis-in">#</a></h3>
<ol>
<li>Midwest Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/986">MidWest-IX - Indy</a>)</li>
</ol>
<h3 id="jacksonville-fl">Jacksonville, FL<a class="zola-anchor" href="#jacksonville-fl" aria-label="Anchor link for: jacksonville-fl">#</a></h3>
<ol>
<li>Jacksonville Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/563">JXIX</a>)</li>
</ol>
<h3 id="kansas-city-mo">Kansas City, MO<a class="zola-anchor" href="#kansas-city-mo" aria-label="Anchor link for: kansas-city-mo">#</a></h3>
<ol>
<li>Kansas City Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/249">KCIX</a>)</li>
</ol>
<h3 id="los-angeles-ca">Los Angeles, CA<a class="zola-anchor" href="#los-angeles-ca" aria-label="Anchor link for: los-angeles-ca">#</a></h3>
<ol>
<li>CENIC International Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/124">CIIX</a>)</li>
<li>Equinix Los Angeles Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/4">Equinix Los Angeles</a>)</li>
<li>Los Angeles International Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/23">LAIIX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/16">MAE West</a></li>
<li>Pacific Wave Exchange in Los Angeles and Seattle (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/82">PacificWave</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/142">CoreSite - Any2 California</a></li>
</ol>
<h3 id="madison-wi">Madison, WI<a class="zola-anchor" href="#madison-wi" aria-label="Anchor link for: madison-wi">#</a></h3>
<ol>
<li>Madison Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/89">MadIX</a>)</li>
</ol>
<h3 id="manassas-va">Manassas, VA<a class="zola-anchor" href="#manassas-va" aria-label="Anchor link for: manassas-va">#</a></h3>
<ol>
<li>LINX Northern Virginia (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/777">LINX</a>)</li>
</ol>
<h3 id="medford-or">Medford, OR<a class="zola-anchor" href="#medford-or" aria-label="Anchor link for: medford-or">#</a></h3>
<ol>
<li>Southern Oregon Access Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/357">SOAX</a>)</li>
</ol>
<h3 id="miami-fl">Miami, FL<a class="zola-anchor" href="#miami-fl" aria-label="Anchor link for: miami-fl">#</a></h3>
<ol>
<li>Equinix Internet Exchange Miami (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/593">Equinix Miami</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/15">MAE East</a></li>
<li>Miami Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/957">MiamiIX</a>)</li>
<li>NAP of the Americas (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/17">NOTA</a>)</li>
<li>The South Florida Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/954">FL-IX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/205">CoreSite - Any2 Miami</a></li>
</ol>
<h3 id="milwaukee-wi">Milwaukee, WI<a class="zola-anchor" href="#milwaukee-wi" aria-label="Anchor link for: milwaukee-wi">#</a></h3>
<ol>
<li>The Milwaukee IX (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/499">MKE-IX</a>)</li>
</ol>
<h3 id="minneapolis-mn">Minneapolis, MN<a class="zola-anchor" href="#minneapolis-mn" aria-label="Anchor link for: minneapolis-mn">#</a></h3>
<ol>
<li>Midwest Internet Cooperative Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/446">MICE</a>)</li>
</ol>
<h3 id="moffett-field-ca">Moffett Field, CA<a class="zola-anchor" href="#moffett-field-ca" aria-label="Anchor link for: moffett-field-ca">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/180">NGIX West</a></li>
</ol>
<h3 id="nashville-tn">Nashville, TN<a class="zola-anchor" href="#nashville-tn" aria-label="Anchor link for: nashville-tn">#</a></h3>
<ol>
<li>Nashville Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1038">NashIX</a>)</li>
</ol>
<h3 id="new-york-ny">New York, NY<a class="zola-anchor" href="#new-york-ny" aria-label="Anchor link for: new-york-ny">#</a></h3>
<ol>
<li>AMS-IX New York (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/806">AMS-IX NY</a>)</li>
<li>Big Apple Peering Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/151">BigApe</a>)</li>
<li>Digital Realty / Telx Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/325">TIE</a>)</li>
<li>Equinix Internet Exchange New York (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/12">Equinix New York</a>)</li>
<li>Free NYIIX Alternative (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/41">NYCX</a>)</li>
<li>New York, NY - (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/332">CoreSite - Any2 New York</a>)</li>
<li>DE-CIX, the New York / New Jersey Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/804">DE-CIX New York</a>)</li>
<li>New York International Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/14">NYIIX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/15">MAE East</a></li>
</ol>
<h3 id="omaha-ne">Omaha, NE<a class="zola-anchor" href="#omaha-ne" aria-label="Anchor link for: omaha-ne">#</a></h3>
<ol>
<li>Omaha Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/809">OmahaIX</a>)</li>
</ol>
<h3 id="palo-alto-ca">Palo Alto, CA<a class="zola-anchor" href="#palo-alto-ca" aria-label="Anchor link for: palo-alto-ca">#</a></h3>
<ol>
<li>Equinix Internet Exchange Palo Alto (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/7">Equinix Palo Alto</a>)</li>
</ol>
<h3 id="philadelphia-pa">Philadelphia, PA<a class="zola-anchor" href="#philadelphia-pa" aria-label="Anchor link for: philadelphia-pa">#</a></h3>
<ol>
<li>Philadelphia Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/433">PHILAIX</a>)</li>
</ol>
<h3 id="phoenix-az">Phoenix, AZ<a class="zola-anchor" href="#phoenix-az" aria-label="Anchor link for: phoenix-az">#</a></h3>
<ol>
<li>Arizona Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/476">AZIX</a>)</li>
<li>Digital Realty / Telx Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/256">TIE</a>)</li>
<li>Phoenix Internet Exchange, LLC (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/130">PHX-IX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/662">Phoenix IX</a></li>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/760">CyrusOne IX</a>)</li>
</ol>
<h3 id="portland-or">Portland, OR<a class="zola-anchor" href="#portland-or" aria-label="Anchor link for: portland-or">#</a></h3>
<ol>
<li>Central Oregon Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/514">COIX</a>)</li>
<li>Northwest Access Exchange, Inc. (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/165">NWAX</a>)</li>
<li>Oregon Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/127">OIX</a>)</li>
</ol>
<h3 id="reno-nv">Reno, NV<a class="zola-anchor" href="#reno-nv" aria-label="Anchor link for: reno-nv">#</a></h3>
<ol>
<li>Tahoe Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/938">TahoeIX</a>)</li>
</ol>
<h3 id="reston-va">Reston, VA<a class="zola-anchor" href="#reston-va" aria-label="Anchor link for: reston-va">#</a></h3>
<ol>
<li>LINX Northern Virginia (<a rel="noopener nofollow noreferrer" target="_blank" href="https://peeringdb.com/ix/777">LINX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/15">MAE East</a></li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/204">CoreSite - Any2 NorthEast</a></li>
</ol>
<h3 id="saint-george-ut">Saint George, UT<a class="zola-anchor" href="#saint-george-ut" aria-label="Anchor link for: saint-george-ut">#</a></h3>
<ol>
<li>Southern Utah Peering Regional Network (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/363">SUPRnet</a>)</li>
</ol>
<h3 id="salt-lake-city-ut">Salt Lake City, UT<a class="zola-anchor" href="#salt-lake-city-ut" aria-label="Anchor link for: salt-lake-city-ut">#</a></h3>
<ol>
<li>Salt Lake Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/829">SLIX</a>)</li>
</ol>
<h3 id="san-antonio-tx">San Antonio, TX<a class="zola-anchor" href="#san-antonio-tx" aria-label="Anchor link for: san-antonio-tx">#</a></h3>
<ol>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/675">CyrusOne IX</a>)</li>
</ol>
<h3 id="san-diego-ca">San Diego, CA<a class="zola-anchor" href="#san-diego-ca" aria-label="Anchor link for: san-diego-ca">#</a></h3>
<ol>
<li>San Diego NAP (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/81">SD-NAP</a>)</li>
</ol>
<h3 id="san-francisco-ca">San Francisco, CA<a class="zola-anchor" href="#san-francisco-ca" aria-label="Anchor link for: san-francisco-ca">#</a></h3>
<ol>
<li>San Francisco Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/32">SFIX</a>)</li>
<li>San Francisco Metropolitan Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/155">SFMIX</a>)</li>
</ol>
<h3 id="san-jose-ca">San Jose, CA<a class="zola-anchor" href="#san-jose-ca" aria-label="Anchor link for: san-jose-ca">#</a></h3>
<ol>
<li>AMS-IX Bay Area (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/935">AMS-IX BA</a></li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/338">CoreSite - Any2 Northern California</a>)</li>
<li>Equinix San Jose / Bay Area Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/5">Equinix San Jose</a>)</li>
<li>NASA Ames Internet eXchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/428">AIX</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/16">MAE West</a></li>
</ol>
<h3 id="san-juan-puerto-rico">San Juan, Puerto Rico<a class="zola-anchor" href="#san-juan-puerto-rico" aria-label="Anchor link for: san-juan-puerto-rico">#</a></h3>
<ol>
<li>Internet Exchange of Puerto Rico (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/137">IX.PR</a>)</li>
<li>Puerto Rico Bridge Initiative (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1061">PRBI-IX</a>)</li>
</ol>
<h3 id="seattle-wa">Seattle, WA<a class="zola-anchor" href="#seattle-wa" aria-label="Anchor link for: seattle-wa">#</a></h3>
<ol>
<li>Megaport MegaIX Seattle (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1174">MegaIX Seattle</a>)</li>
<li>Pacific Wave Exchange in Los Angeles and Seattle (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/82">PacificWave</a>)</li>
<li>Seattle Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/13">SIX</a>)</li>
<li>Seattle Internet Exchange (9000 MTU) (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1285">SIX Seattle (Jumbo)</a>)</li>
<li>Seattle, WA Equinix Internet Exchange Seattle (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/11">Equinix Seattle</a>)</li>
</ol>
<h3 id="sterling-va">Sterling, VA<a class="zola-anchor" href="#sterling-va" aria-label="Anchor link for: sterling-va">#</a></h3>
<ol>
<li>CyrusOne Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1117">CyrusOne IX</a>)</li>
</ol>
<h3 id="tampa-fl">Tampa, FL<a class="zola-anchor" href="#tampa-fl" aria-label="Anchor link for: tampa-fl">#</a></h3>
<ol>
<li>Tampa Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/141">TampaIX</a>)</li>
<li>Tampa Internet Exchange (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/833">TPAIX</a>)</li>
</ol>
<h3 id="tulsa-ok">Tulsa, OK<a class="zola-anchor" href="#tulsa-ok" aria-label="Anchor link for: tulsa-ok">#</a></h3>
<ol>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/1058">LiveAir Tulsa IX</a></li>
</ol>
<h3 id="vienna-va">Vienna, VA<a class="zola-anchor" href="#vienna-va" aria-label="Anchor link for: vienna-va">#</a></h3>
<ol>
<li>Equinix Internet Exchange Vienna, VA (<a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/10">Equinix Vienna (VA)</a>)</li>
<li><a rel="noopener nofollow noreferrer" target="_blank" href="https://www.peeringdb.com/ix/15">MAE East</a></li>
</ol>
</content>
</entry>
</feed>