Add cloudflare peer IDs

[mathew-cf]

No description provided.

[welcome]

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.
• Your contribution itself is clear (grammar and spelling checked, any code blocks checked and commented) and in its best form. Follow the docs contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.
• The PR gets reviews, discussed and approvals as needed.
• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

[aschmahmann]

@mathew-cf are you sure these peerIDs are correct and reachable? Having some trouble dialing them. For example: https://ipfs-check.on.fleek.co/?cid=QmfMYyn8LUWEfRXfijKFjBAshSsPVRUgwLZzsD7kcTtX1A&multiaddr=%2Fdnsaddr%2Fbootstrap.cloudflare-ipfs.com%2Fipfs%2FQmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE

[mathew-cf]

I'm still working on opening up ingress to the IP. May have been a bit too early with this PR

[johnnymatthews]

Looks like you're still working on this. I'm gonna convert it to a draft. Ping folks when you're ready for a review.

[mathew-cf]

This is ready for review. Our peer count limit is fairly low as of right now but you should be able to ping our nodes without issue

$ ipfs ping /dnsaddr/node-12.ingress.cloudflare-ipfs.com/ipfs/QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev
PING QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev.
Pong received: time=70.94 ms
Pong received: time=94.22 ms
Pong received: time=83.20 ms
Pong received: time=74.81 ms
Pong received: time=74.89 ms
Pong received: time=79.82 ms
Pong received: time=75.27 ms
Pong received: time=71.42 ms
Pong received: time=70.23 ms
Pong received: time=80.62 ms
Average latency: 77.54ms

[johnnymatthews]

Nice. I tried pinging (ipfs ping ...) each of them, and got a pong from most. I'll merge this now.

Edit: actually, I'd like to make sure that all the peers can be reached.

[johnnymatthews]

I can't reach these three nodes:

QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z
QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx
QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G

Are they actually up? I'm at an airport, so there's a chance that the WiFi here is bugging out.

[isaadabbasi]

I can't reach these three nodes:

QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z
QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx
QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G

I verified and still these 3 nodes are unreachable. Any update on this?

[johnnymatthews]

I can't reach these three nodes:

QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z
QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx
QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G

I verified and still these 3 nodes are unreachable. Any update on this?

I just tried this again. The first and last gave me a pong! But the middle (QmcfJ...Uswx) didnt:

$ › ipfs ping QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z
PING QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z.
Pong received: time=145.87 ms

$ › ipfs ping QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx
Looking up peer QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx
PING QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx.
Ping error: failed to dial QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx:
  * [/ip4/136.144.57.127/tcp/4002/ws/p2p/12D3KooWJbARcvvEEF4AAqvAEaVYRkEUNPC3Rv3joebqfPh4LaKq/p2p-circuit] dial backoff
  * [/ip6/2604:1380:45f1:4d00::3/tcp/4002/ws/p2p/12D3KooWJbARcvvEEF4AAqvAEaVYRkEUNPC3Rv3joebqfPh4LaKq/p2p-circuit] error opening hop stream to relay: context deadline exceeded
  * [/ip4/136.144.57.127/tcp/4001/p2p/12D3KooWJbARcvvEEF4AAqvAEaVYRkEUNPC3Rv3joebqfPh4LaKq/p2p-circuit] error opening relay circuit: NO_RESERVATION (204)
  * [/ip6/2604:1380:45f1:4d00::3/tcp/4001/p2p/12D3KooWJbARcvvEEF4AAqvAEaVYRkEUNPC3Rv3joebqfPh4LaKq/p2p-circuit] concurrent active dial through the same relay failed with a protocol error
Error: ping failed

$ › ipfs ping QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G
Looking up peer QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G
PING QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G.
Pong received: time=85.61 ms

[2color]

Just ran a test to ping all the nodes and they were all reachable

I got a few Error: peer lookup failed: routing: not found but after trying a couple of times it worked and I got a Pong received.

Peer ID	ipfs ping peerId
QmcFf2FH3CEgTNHeMRGhN7HNHU1EXAxoEk6EFuSyXCsvRE	✅
QmcFmLd5ySfk2WZuJ1mfSWLDjdmHZq7rSAua4GoeSQfs1z	✅
QmcfFmzSDVbwexQ9Au2pt5YEXHK5xajwgaU6PpkbLWerMa	✅
QmcfJeB3Js1FG7T8YaZATEiaHqNKVdQfybYYkbT1knUswx	✅
QmcfVvzK4tMdFmpJjEKDUoqRgP4W9FnmJoziYX5GXJJ8eZ	✅
QmcfZD3VKrUxyP9BbyUnZDpbqDnT7cQ4WjPP8TRLXaoE7G	✅
QmcfZP2LuW4jxviTeG8fi28qjnZScACb8PEgHAc17ZEri3	✅
QmcfgsJsMtx6qJb74akCw1M24X1zFwgGo11h1cuhwQjtJP	✅
Qmcfr2FC7pFzJbTSDfYaSy1J8Uuy8ccGLeLyqJCKJvTHMi	✅
QmcfR3V5YAtHBzxVACWCzXTt26SyEkxdwhGJ6875A8BuWx	✅
Qmcfuo1TM9uUiJp6dTbm915Rf1aTqm3a3dnmCdDQLHgvL5	✅
QmcfV2sg9zaq7UUHVCGuSvT2M2rnLBAPsiE79vVyK3Cuev	✅

[johnnymatthews]

Tried all the peers again and got responses from everything! Merging!