Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/protocol/upptime-pln

Site monitoring for PL sites.
https://github.com/protocol/upptime-pln

Last synced: about 1 year ago
JSON representation

Site monitoring for PL sites.

Awesome Lists containing this project

README 

          
# [📈 Live Status](https://upptime.outercore.ai):  **🟧 Partial outage**



This repository contains the open-source uptime monitor and status page for [Protocol Labs](https://upptime.outercore.ai), powered by [Upptime](https://github.com/upptime/upptime).



The [Airtable Interface](https://airtable.com/invite/l?inviteId=invVgVQUtAq60QRrA&inviteToken=db142bb642208b5ba9943e1c02ddb083db68ceef4bf45667fa7a2dd17c136b48&utm_medium=email&utm_source=product_team&utm_content=transactional-alerts) can be used to create a Pull Request to Add or Omit monitoring for specific sites, as well as to add your Github handle to receive notifications for specific sites. Please check the [Upptime Configuration](https://upptime.js.org/docs/configuration) docs for more advanced config options, some of which are included in the Airtable interface.



Do not add sites that do not exist in Airtable. They will be overwritten by an automated flow that happens weekly (currently) which collects known active domains via API. Open an issue if you would like to add additional data sources.



Global notifications are posted to the [#upptime-pln](https://filecoinproject.slack.com/archives/C05NN527TS7) channel on Filecoin Slack.



[![Uptime CI](https://github.com/vesahc/upptime-pln/workflows/Uptime%20CI/badge.svg)](https://github.com/vesahc/upptime-pln/actions?query=workflow%3A%22Uptime+CI%22)

[![Response Time CI](https://github.com/vesahc/upptime-pln/workflows/Response%20Time%20CI/badge.svg)](https://github.com/vesahc/upptime-pln/actions?query=workflow%3A%22Response+Time+CI%22)

[![Graphs CI](https://github.com/vesahc/upptime-pln/workflows/Graphs%20CI/badge.svg)](https://github.com/vesahc/upptime-pln/actions?query=workflow%3A%22Graphs+CI%22)

[![Static Site CI](https://github.com/vesahc/upptime-pln/workflows/Static%20Site%20CI/badge.svg)](https://github.com/vesahc/upptime-pln/actions?query=workflow%3A%22Static+Site+CI%22)

[![Summary CI](https://github.com/vesahc/upptime-pln/workflows/Summary%20CI/badge.svg)](https://github.com/vesahc/upptime-pln/actions?query=workflow%3A%22Summary+CI%22)



With [Upptime](https://upptime.js.org), you can get your own unlimited and free uptime monitor and status page, powered entirely by a GitHub repository. We use [Issues](https://github.com/vesahc/upptime-pln/issues) as incident reports, [Actions](https://github.com/vesahc/upptime-pln/actions) as uptime monitors, and [Pages](https://upptime.outercore.ai) for the status page.



| URL | Status | History | Response Time | Uptime |

| --- | ------ | ------- | ------------- | ------ |

|  [2019.ipfs.camp](https://2019.ipfs.camp) | 🟩 Up | [2019-ipfs-camp.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/2019-ipfs-camp.yml) | Response time graph 1110ms
Response time 1223
24-hour response time 983
7-day response time 1110
30-day response time 974
1-year response time 1427 | 100.00%All-time uptime 96.88%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 99.99%
1-year uptime 95.29%

|  [2022.ipfs-thing.events](https://2022.ipfs-thing.events) | 🟩 Up | [2022-ipfs-thing-events.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/2022-ipfs-thing-events.yml) | Response time graph 683ms
Response time 785
24-hour response time 632
7-day response time 683
30-day response time 986
1-year response time 756 | 100.00%All-time uptime 93.16%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 36.57%
1-year uptime 89.68%

|  [2022.ipfs-thing.io](https://2022.ipfs-thing.io) | 🟩 Up | [2022-ipfs-thing-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/2022-ipfs-thing-io.yml) | Response time graph 413ms
Response time 434
24-hour response time 563
7-day response time 413
30-day response time 295
1-year response time 433 | 100.00%All-time uptime 93.08%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 34.90%
1-year uptime 89.55%

|  [2022.ipfs.camp](https://2022.ipfs.camp) | 🟩 Up | [2022-ipfs-camp.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/2022-ipfs-camp.yml) | Response time graph 939ms
Response time 1207
24-hour response time 843
7-day response time 939
30-day response time 859
1-year response time 1492 | 100.00%All-time uptime 84.93%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 77.21%

|  [2023.ipfs-thing.io](https://2023.ipfs-thing.io) | 🟩 Up | [2023-ipfs-thing-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/2023-ipfs-thing-io.yml) | Response time graph 789ms
Response time 1043
24-hour response time 776
7-day response time 789
30-day response time 745
1-year response time 1270 | 100.00%All-time uptime 99.88%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.82%

|  [22.labweek.io](https://22.labweek.io) | 🟩 Up | [22-labweek-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/22-labweek-io.yml) | Response time graph 227ms
Response time 417
24-hour response time 162
7-day response time 227
30-day response time 208
1-year response time 429 | 100.00%All-time uptime 85.90%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 78.69%

|  [ar.dev.wikipedia-on-ipfs.org](https://ar.dev.wikipedia-on-ipfs.org) | 🟩 Up | [ar-dev-wikipedia-on-ipfs-org.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/ar-dev-wikipedia-on-ipfs-org.yml) | Response time graph 680ms
Response time 548
24-hour response time 749
7-day response time 680
30-day response time 595
1-year response time 635 | 12.46%All-time uptime 97.50%
24-hour uptime 0.00%
7-day uptime 12.46%
30-day uptime 79.86%
1-year uptime 96.28%

|  [ar.wikipedia-on-ipfs.org](https://ar.wikipedia-on-ipfs.org) | 🟩 Up | [ar-wikipedia-on-ipfs-org.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/ar-wikipedia-on-ipfs-org.yml) | Response time graph 250ms
Response time 325
24-hour response time 168
7-day response time 250
30-day response time 268
1-year response time 347 | 100.00%All-time uptime 99.51%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.52%

|  [archive.discuss.filecoin.io](https://archive.discuss.filecoin.io) | 🟥 Down | [archive-discuss-filecoin-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/archive-discuss-filecoin-io.yml) | Response time graph 0ms
Response time 866
24-hour response time 0
7-day response time 0
30-day response time 0
1-year response time 991 | 0.00%All-time uptime 59.85%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 40.29%

|  [arewedistributedyet.com](https://arewedistributedyet.com) | 🟩 Up | [arewedistributedyet-com.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/arewedistributedyet-com.yml) | Response time graph 398ms
Response time 792
24-hour response time 766
7-day response time 398
30-day response time 465
1-year response time 829 | 100.00%All-time uptime 96.61%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 73.74%
1-year uptime 94.87%

|  [areweinterplanetaryyet.org](https://areweinterplanetaryyet.org) | 🟩 Up | [areweinterplanetaryyet-org.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/areweinterplanetaryyet-org.yml) | Response time graph 718ms
Response time 897
24-hour response time 675
7-day response time 718
30-day response time 789
1-year response time 1036 | 0.00%All-time uptime 91.56%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 31.32%
1-year uptime 89.29%

|  [arg.protocol.ai](https://arg.protocol.ai) | 🟩 Up | [arg-protocol-ai.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/arg-protocol-ai.yml) | Response time graph 265ms
Response time 365
24-hour response time 157
7-day response time 265
30-day response time 321
1-year response time 380 | 100.00%All-time uptime 81.95%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 72.71%

|  [awesome.ipfs.tech](https://awesome.ipfs.tech) | 🟩 Up | [awesome-ipfs-tech.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/awesome-ipfs-tech.yml) | Response time graph 180ms
Response time 160
24-hour response time 129
7-day response time 180
30-day response time 135
1-year response time 174 | 100.00%All-time uptime 99.98%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%

|  [badbits.dwebops.pub](https://badbits.dwebops.pub) | 🟩 Up | [badbits-dwebops-pub.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/badbits-dwebops-pub.yml) | Response time graph 174ms
Response time 275
24-hour response time 100
7-day response time 174
30-day response time 181
1-year response time 285 | 99.54%All-time uptime 99.54%
24-hour uptime 100.00%
7-day uptime 99.54%
30-day uptime 98.76%
1-year uptime 99.36%

|  [benchmark-js.ipfs.io](https://benchmark-js.ipfs.io) | 🟩 Up | [benchmark-js-ipfs-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/benchmark-js-ipfs-io.yml) | Response time graph 145ms
Response time 214
24-hour response time 242
7-day response time 145
30-day response time 148
1-year response time 231 | 99.54%All-time uptime 99.64%
24-hour uptime 100.00%
7-day uptime 99.54%
30-day uptime 99.90%
1-year uptime 99.51%

|  [blocks.ipfs.io](https://blocks.ipfs.io) | 🟩 Up | [blocks-ipfs-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/blocks-ipfs-io.yml) | Response time graph 138ms
Response time 191
24-hour response time 115
7-day response time 138
30-day response time 129
1-year response time 205 | 100.00%All-time uptime 97.30%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 99.98%
1-year uptime 99.50%

|  [blog.ipfs.io](https://blog.ipfs.io) | 🟩 Up | [blog-ipfs-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/blog-ipfs-io.yml) | Response time graph 357ms
Response time 433
24-hour response time 380
7-day response time 357
30-day response time 386
1-year response time 353 | 100.00%All-time uptime 99.98%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.97%

|  [blog.ipfs.tech](https://blog.ipfs.tech) | 🟩 Up | [blog-ipfs-tech.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/blog-ipfs-tech.yml) | Response time graph 79ms
Response time 173
24-hour response time 44
7-day response time 79
30-day response time 47
1-year response time 111 | 100.00%All-time uptime 99.98%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.98%

|  [blog.libp2p.io](https://blog.libp2p.io) | 🟩 Up | [blog-libp2p-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/blog-libp2p-io.yml) | Response time graph 745ms
Response time 518
24-hour response time 743
7-day response time 745
30-day response time 707
1-year response time 567 | 100.00%All-time uptime 81.14%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 71.48%

|  [boost.filecoin.io](https://boost.filecoin.io) | 🟩 Up | [boost-filecoin-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/boost-filecoin-io.yml) | Response time graph 857ms
Response time 329
24-hour response time 598
7-day response time 857
30-day response time 829
1-year response time 348 | 100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%

|  [boston23.sbs.tech](https://boston23.sbs.tech) | 🟩 Up | [boston23-sbs-tech.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/boston23-sbs-tech.yml) | Response time graph 601ms
Response time 452
24-hour response time 728
7-day response time 601
30-day response time 634
1-year response time 493 | 100.00%All-time uptime 99.99%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.99%

|  [breakthroughs-in-computing.labweek.io](https://breakthroughs-in-computing.labweek.io) | 🟥 Down | [breakthroughs-in-computing-labweek-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/breakthroughs-in-computing-labweek-io.yml) | Response time graph 299ms
Response time 284
24-hour response time 370
7-day response time 299
30-day response time 305
1-year response time 307 | 0.00%All-time uptime 74.61%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 61.64%

|  [buildingweb3.com](https://buildingweb3.com) | 🟥 Down | [buildingweb3-com.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/buildingweb3-com.yml) | Response time graph 0ms
Response time 760
24-hour response time 0
7-day response time 0
30-day response time 0
1-year response time 800 | 0.00%All-time uptime 76.53%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 0.00%
1-year uptime 64.35%

|  [car.ipfs.io](https://car.ipfs.io) | 🟩 Up | [car-ipfs-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/car-ipfs-io.yml) | Response time graph 381ms
Response time 601
24-hour response time 448
7-day response time 381
30-day response time 915
1-year response time 584 | 100.00%All-time uptime 62.05%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 54.30%
1-year uptime 42.62%

|  [check.ipfs.network](https://check.ipfs.network) | 🟩 Up | [check-ipfs-network.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/check-ipfs-network.yml) | Response time graph 475ms
Response time 628
24-hour response time 585
7-day response time 475
30-day response time 408
1-year response time 605 | 0.00%All-time uptime 94.85%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 28.29%
1-year uptime 93.70%

|  [cid.ipfs.io](https://cid.ipfs.io) | 🟩 Up | [cid-ipfs-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/cid-ipfs-io.yml) | Response time graph 355ms
Response time 585
24-hour response time 436
7-day response time 355
30-day response time 882
1-year response time 602 | 100.00%All-time uptime 69.72%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 24.71%
1-year uptime 62.92%

|  [cid.ipfs.tech](https://cid.ipfs.tech) | 🟩 Up | [cid-ipfs-tech.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/cid-ipfs-tech.yml) | Response time graph 248ms
Response time 257
24-hour response time 478
7-day response time 248
30-day response time 182
1-year response time 268 | 100.00%All-time uptime 95.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 69.53%
1-year uptime 92.44%

|  [collab.ipfscluster.io](https://collab.ipfscluster.io) | 🟩 Up | [collab-ipfscluster-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/collab-ipfscluster-io.yml) | Response time graph 1167ms
Response time 229
24-hour response time 134
7-day response time 1167
30-day response time 431
1-year response time 253 | 100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%

|  [conformance.ipfs.tech](https://conformance.ipfs.tech) | 🟩 Up | [conformance-ipfs-tech.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/conformance-ipfs-tech.yml) | Response time graph 461ms
Response time 589
24-hour response time 700
7-day response time 461
30-day response time 611
1-year response time 587 | 0.00%All-time uptime 81.59%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 65.03%
1-year uptime 76.66%

|  [connectivity.libp2p.io](https://connectivity.libp2p.io) | 🟩 Up | [connectivity-libp2p-io.yml](https://github.com/protocol/upptime-pln/commits/HEAD/history/connectivity-libp2p-io.yml) | Response time graph 816ms
Response time 719
24-hour response time 1057
7-day response time 816
30-day response time 753
1-year response time 826 | 100.00%All-time uptime 67.84%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 51.38%

|  [consensus-factory.io](https:/