├── .github ├── dependabot.yml └── workflows │ ├── health-check.yml │ └── pull-docker-image.yml ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── health-check.sh ├── index.html ├── logo.svg ├── logs ├── amazon_errors.log ├── amazon_report.log ├── apple_errors.log ├── apple_report.log ├── bing_errors.log ├── bing_report.log ├── cloudflare_errors.log ├── cloudflare_report.log ├── dropbox_errors.log ├── dropbox_report.log ├── facebook_errors.log ├── facebook_report.log ├── github_report.log ├── google_errors.log ├── google_report.log ├── instagram_errors.log ├── instagram_report.log ├── linkedin_errors.log ├── linkedin_report.log ├── microsoft_errors.log ├── microsoft_report.log ├── netflix_errors.log ├── netflix_report.log ├── netlify_errors.log ├── netlify_report.log ├── popular_report.log ├── reddit_errors.log ├── reddit_report.log ├── spotify_errors.log ├── spotify_report.log ├── twitter_errors.log ├── twitter_report.log ├── vercel_errors.log ├── vercel_report.log ├── websites_errors.log ├── websites_report.log ├── wikipedia_report.log ├── yahoo_errors.log ├── yahoo_report.log └── youtube_report.log ├── main.js ├── style.css └── urls.cfg /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | version: 2 2 | updates: 3 | - package-ecosystem: "github-actions" 4 | directory: "/" 5 | schedule: 6 | interval: "daily" 7 | -------------------------------------------------------------------------------- /.github/workflows/health-check.yml: -------------------------------------------------------------------------------- 1 | name: Scheduled Health Check 2 | 3 | # Controls when the action will run. 4 | on: 5 | schedule: 6 | - cron: "0,15,30,45 * * * *" 7 | workflow_dispatch: 8 | 9 | jobs: 10 | health_check_job: 11 | strategy: 12 | matrix: 13 | os: ['ubuntu-24.04'] 14 | runs-on: ${{ matrix.os }} 15 | name: Check all sites 16 | steps: 17 | - name: Checkout Code 18 | uses: actions/checkout@v4.1.6 19 | 20 | - name: Install 21 | run: npm i -g smart-audit-cli 22 | 23 | - name: Run Shell Script 24 | id: shell_script_run 25 | run: bash ./health-check.sh 26 | -------------------------------------------------------------------------------- /.github/workflows/pull-docker-image.yml: -------------------------------------------------------------------------------- 1 | name: Pull Docker Image on Schedule 2 | 3 | on: 4 | schedule: 5 | - cron: "0,15,30,45 * * * *" 6 | workflow_dispatch: 7 | 8 | jobs: 9 | pull-docker-image: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - name: 📦 Checkout 13 | uses: actions/checkout@v4 14 | 15 | - name: ⬇️ Pull Docker Image 16 | run: | 17 | IMAGE_NAME="ghcr.io/louislam/uptime-kuma:nightly2" 18 | docker pull $IMAGE_NAME 19 | echo "Image pulled at: $(date)" 20 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We as members, contributors, and leaders pledge to make participation in our 6 | community a harassment-free experience for everyone, regardless of age, body 7 | size, visible or invisible disability, ethnicity, sex characteristics, gender 8 | identity and expression, level of experience, education, socio-economic status, 9 | nationality, personal appearance, race, religion, or sexual identity 10 | and orientation. 11 | 12 | We pledge to act and interact in ways that contribute to an open, welcoming, 13 | diverse, inclusive, and healthy community. 14 | 15 | ## Our Standards 16 | 17 | Examples of behavior that contributes to a positive environment for our 18 | community include: 19 | 20 | * Demonstrating empathy and kindness toward other people 21 | * Being respectful of differing opinions, viewpoints, and experiences 22 | * Giving and gracefully accepting constructive feedback 23 | * Accepting responsibility and apologizing to those affected by our mistakes, 24 | and learning from the experience 25 | * Focusing on what is best not just for us as individuals, but for the 26 | overall community 27 | 28 | Examples of unacceptable behavior include: 29 | 30 | * The use of sexualized language or imagery, and sexual attention or 31 | advances of any kind 32 | * Trolling, insulting or derogatory comments, and personal or political attacks 33 | * Public or private harassment 34 | * Publishing others' private information, such as a physical or email 35 | address, without their explicit permission 36 | * Other conduct which could reasonably be considered inappropriate in a 37 | professional setting 38 | 39 | ## Enforcement Responsibilities 40 | 41 | Community leaders are responsible for clarifying and enforcing our standards of 42 | acceptable behavior and will take appropriate and fair corrective action in 43 | response to any behavior that they deem inappropriate, threatening, offensive, 44 | or harmful. 45 | 46 | Community leaders have the right and responsibility to remove, edit, or reject 47 | comments, commits, code, wiki edits, issues, and other contributions that are 48 | not aligned to this Code of Conduct, and will communicate reasons for moderation 49 | decisions when appropriate. 50 | 51 | ## Scope 52 | 53 | This Code of Conduct applies within all community spaces, and also applies when 54 | an individual is officially representing the community in public spaces. 55 | Examples of representing our community include using an official e-mail address, 56 | posting via an official social media account, or acting as an appointed 57 | representative at an online or offline event. 58 | 59 | ## Enforcement 60 | 61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 62 | reported to the community leaders responsible for enforcement at 63 | pzhafeez@gmail.com. 64 | All complaints will be reviewed and investigated promptly and fairly. 65 | 66 | All community leaders are obligated to respect the privacy and security of the 67 | reporter of any incident. 68 | 69 | ## Enforcement Guidelines 70 | 71 | Community leaders will follow these Community Impact Guidelines in determining 72 | the consequences for any action they deem in violation of this Code of Conduct: 73 | 74 | ### 1. Correction 75 | 76 | **Community Impact**: Use of inappropriate language or other behavior deemed 77 | unprofessional or unwelcome in the community. 78 | 79 | **Consequence**: A private, written warning from community leaders, providing 80 | clarity around the nature of the violation and an explanation of why the 81 | behavior was inappropriate. A public apology may be requested. 82 | 83 | ### 2. Warning 84 | 85 | **Community Impact**: A violation through a single incident or series 86 | of actions. 87 | 88 | **Consequence**: A warning with consequences for continued behavior. No 89 | interaction with the people involved, including unsolicited interaction with 90 | those enforcing the Code of Conduct, for a specified period of time. This 91 | includes avoiding interactions in community spaces as well as external channels 92 | like social media. Violating these terms may lead to a temporary or 93 | permanent ban. 94 | 95 | ### 3. Temporary Ban 96 | 97 | **Community Impact**: A serious violation of community standards, including 98 | sustained inappropriate behavior. 99 | 100 | **Consequence**: A temporary ban from any sort of interaction or public 101 | communication with the community for a specified period of time. No public or 102 | private interaction with the people involved, including unsolicited interaction 103 | with those enforcing the Code of Conduct, is allowed during this period. 104 | Violating these terms may lead to a permanent ban. 105 | 106 | ### 4. Permanent Ban 107 | 108 | **Community Impact**: Demonstrating a pattern of violation of community 109 | standards, including sustained inappropriate behavior, harassment of an 110 | individual, or aggression toward or disparagement of classes of individuals. 111 | 112 | **Consequence**: A permanent ban from any sort of public interaction within 113 | the community. 114 | 115 | ## Attribution 116 | 117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], 118 | version 2.0, available at 119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. 120 | 121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct 122 | enforcement ladder](https://github.com/mozilla/diversity). 123 | 124 | [homepage]: https://www.contributor-covenant.org 125 | 126 | For answers to common questions about this code of conduct, see the FAQ at 127 | https://www.contributor-covenant.org/faq. Translations are available at 128 | https://www.contributor-covenant.org/translations. 129 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 DevMirza 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Status Page [Live Demo](https://islam-is-best-religion.cyclonebotlist.ml) 2 | 3 | ![GitHub commit activity (branch)](https://img.shields.io/github/commit-activity/m/Zaid-maker/status-page?logo=github) [![Scheduled Health Check](https://github.com/Zaid-maker/status-page/actions/workflows/health-check.yml/badge.svg)](https://github.com/Zaid-maker/status-page/actions/workflows/health-check.yml) [![pages-build-deployment](https://github.com/Zaid-maker/status-page/actions/workflows/pages/pages-build-deployment/badge.svg)](https://github.com/Zaid-maker/status-page/actions/workflows/pages/pages-build-deployment) [![CodeFactor](https://www.codefactor.io/repository/github/zaid-maker/status-page/badge)](https://www.codefactor.io/repository/github/zaid-maker/status-page) 4 | 5 | Status page written in pure JS/HTML/CSS. Self-hosted on Github Pages and Github Actions 6 | -------------------------------------------------------------------------------- /health-check.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | commit=true 4 | origin=$(git remote get-url origin) 5 | if [[ $origin == *Zaid-maker/status-page* ]] 6 | then 7 | commit=true 8 | fi 9 | 10 | KEYSARRAY=() 11 | URLSARRAY=() 12 | 13 | urlsConfig="./urls.cfg" 14 | echo "Reading $urlsConfig" 15 | while read -r line 16 | do 17 | echo " $line" 18 | IFS='=' read -ra TOKENS <<< "$line" 19 | KEYSARRAY+=(${TOKENS[0]}) 20 | URLSARRAY+=(${TOKENS[1]}) 21 | done < "$urlsConfig" 22 | 23 | echo "********************" 24 | echo "Starting health checks with ${#KEYSARRAY[@]} configs:" 25 | 26 | mkdir -p logs 27 | 28 | # Set max log entries for 30 days of retention 29 | MAX_LOG_ENTRIES=8640 30 | 31 | for (( index=0; index < ${#KEYSARRAY[@]}; index++)) 32 | do 33 | key="${KEYSARRAY[index]}" 34 | url="${URLSARRAY[index]}" 35 | echo " $key=$url" 36 | 37 | for i in 1 2 3 4; 38 | do 39 | # Customized curl with timeout, retry, and output on error 40 | response=$(curl --write-out '%{http_code}' --silent --output /dev/null \ 41 | --max-time 10 --retry 2 --retry-delay 5 "$url") 42 | 43 | if [[ "$response" -eq 200 ]] || [[ "$response" -eq 202 ]] || [[ "$response" -eq 301 ]] || [[ "$response" -eq 307 ]]; then 44 | result="success" 45 | else 46 | result="failed" 47 | # Log error details if failed 48 | echo "Error accessing $url, response code: $response" >> "logs/${key}_errors.log" 49 | fi 50 | 51 | if [[ "$result" = "success" ]]; then 52 | break 53 | fi 54 | sleep 5 55 | done 56 | dateTime=$(date +'%Y-%m-%d %H:%M') 57 | if [[ $commit == true ]] 58 | then 59 | echo "$dateTime, $result" >> "logs/${key}_report.log" 60 | # Limit the log entries to 8640 for 30-day retention 61 | tail -n "$MAX_LOG_ENTRIES" "logs/${key}_report.log" > "logs/${key}_report.tmp" 62 | mv "logs/${key}_report.tmp" "logs/${key}_report.log" 63 | else 64 | echo " $dateTime, $result" 65 | fi 66 | done 67 | 68 | if [[ $commit == true ]] 69 | then 70 | # Git configuration for automated commits 71 | git config --global user.name 'Zaid-maker' 72 | git config --global user.email 'pzhafeez@gmail.com' 73 | git add -A --force logs/ 74 | git commit -am '[Automated] Update Health Check Logs' 75 | git push 76 | fi 77 | -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 16 | 20 | Status Page 21 | 22 | 23 |
24 |
25 | Logo 26 | System Status 27 |
28 |
29 |
30 |
31 |
32 |

Incident Reports

33 |
34 |

Active Reports

35 |
36 | Loading... 37 |
38 |
39 |

Past Reports

40 |
41 | Loading... 42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 | 74 |
75 | 86 | 87 | 88 | 94 | 95 | -------------------------------------------------------------------------------- /logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | Group 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 | -------------------------------------------------------------------------------- /logs/apple_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.apple.com, response code: 302 2 | Error accessing https://www.apple.com, response code: 302 3 | Error accessing https://www.apple.com, response code: 302 4 | Error accessing https://www.apple.com, response code: 302 5 | Error accessing https://www.apple.com, response code: 302 6 | Error accessing https://www.apple.com, response code: 302 7 | Error accessing https://www.apple.com, response code: 302 8 | Error accessing https://www.apple.com, response code: 302 9 | Error accessing https://www.apple.com, response code: 302 10 | Error accessing https://www.apple.com, response code: 302 11 | Error accessing https://www.apple.com, response code: 302 12 | Error accessing https://www.apple.com, response code: 302 13 | Error accessing https://www.apple.com, response code: 302 14 | Error accessing https://www.apple.com, response code: 302 15 | Error accessing https://www.apple.com, response code: 302 16 | Error accessing https://www.apple.com, response code: 302 17 | -------------------------------------------------------------------------------- /logs/bing_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.bing.com, response code: 2 | -------------------------------------------------------------------------------- /logs/cloudflare_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing , response code: 000 2 | Error accessing , response code: 000 3 | Error accessing , response code: 000 4 | Error accessing , response code: 000 5 | Error accessing https://www.cloudflare.com, response code: 6 | Error accessing https://www.cloudflare.com, response code: 7 | -------------------------------------------------------------------------------- /logs/dropbox_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing , response code: 000 2 | Error accessing , response code: 000 3 | Error accessing , response code: 000 4 | Error accessing , response code: 000 5 | Error accessing https://www.dropbox.com, response code: 6 | Error accessing https://www.dropbox.com, response code: 7 | Error accessing https://www.dropbox.com, response code: 8 | Error accessing https://www.dropbox.com, response code: 9 | Error accessing https://www.dropbox.com, response code: 000 10 | Error accessing https://www.dropbox.com, response code: 000 11 | Error accessing https://www.dropbox.com, response code: 12 | Error accessing https://www.dropbox.com, response code: 13 | Error accessing https://www.dropbox.com, response code: 14 | Error accessing https://www.dropbox.com, response code: 15 | Error accessing https://www.dropbox.com, response code: 16 | Error accessing https://www.dropbox.com, response code: 17 | -------------------------------------------------------------------------------- /logs/google_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.google.com, response code: 302 2 | Error accessing https://www.google.com, response code: 302 3 | Error accessing https://www.google.com, response code: 302 4 | Error accessing https://www.google.com, response code: 302 5 | -------------------------------------------------------------------------------- /logs/instagram_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.instagram.com, response code: 302 2 | Error accessing https://www.instagram.com, response code: 302 3 | Error accessing https://www.instagram.com, response code: 302 4 | Error accessing https://www.instagram.com, response code: 302 5 | Error accessing https://www.instagram.com, response code: 302 6 | Error accessing https://www.instagram.com, response code: 302 7 | Error accessing https://www.instagram.com, response code: 302 8 | Error accessing https://www.instagram.com, response code: 302 9 | Error accessing https://www.instagram.com, response code: 302 10 | Error accessing https://www.instagram.com, response code: 302 11 | Error accessing https://www.instagram.com, response code: 302 12 | Error accessing https://www.instagram.com, response code: 302 13 | Error accessing https://www.instagram.com, response code: 302 14 | Error accessing https://www.instagram.com, response code: 302 15 | Error accessing https://www.instagram.com, response code: 302 16 | Error accessing https://www.instagram.com, response code: 302 17 | Error accessing https://www.instagram.com, response code: 302 18 | Error accessing https://www.instagram.com, response code: 302 19 | Error accessing https://www.instagram.com, response code: 302 20 | Error accessing https://www.instagram.com, response code: 302 21 | Error accessing https://www.instagram.com, response code: 302 22 | Error accessing https://www.instagram.com, response code: 302 23 | Error accessing https://www.instagram.com, response code: 302 24 | Error accessing https://www.instagram.com, response code: 302 25 | Error accessing https://www.instagram.com, response code: 302 26 | Error accessing https://www.instagram.com, response code: 302 27 | Error accessing https://www.instagram.com, response code: 302 28 | Error accessing https://www.instagram.com, response code: 302 29 | Error accessing https://www.instagram.com, response code: 302 30 | Error accessing https://www.instagram.com, response code: 302 31 | Error accessing https://www.instagram.com, response code: 302 32 | Error accessing https://www.instagram.com, response code: 302 33 | Error accessing https://www.instagram.com, response code: 302 34 | Error accessing https://www.instagram.com, response code: 302 35 | Error accessing https://www.instagram.com, response code: 302 36 | Error accessing https://www.instagram.com, response code: 302 37 | Error accessing https://www.instagram.com, response code: 302 38 | Error accessing https://www.instagram.com, response code: 302 39 | Error accessing https://www.instagram.com, response code: 302 40 | Error accessing https://www.instagram.com, response code: 302 41 | Error accessing https://www.instagram.com, response code: 302 42 | Error accessing https://www.instagram.com, response code: 302 43 | Error accessing https://www.instagram.com, response code: 302 44 | Error accessing https://www.instagram.com, response code: 302 45 | Error accessing https://www.instagram.com, response code: 302 46 | Error accessing https://www.instagram.com, response code: 302 47 | Error accessing https://www.instagram.com, response code: 302 48 | Error accessing https://www.instagram.com, response code: 302 49 | Error accessing https://www.instagram.com, response code: 302 50 | Error accessing https://www.instagram.com, response code: 302 51 | Error accessing https://www.instagram.com, response code: 302 52 | Error accessing https://www.instagram.com, response code: 302 53 | Error accessing https://www.instagram.com, response code: 302 54 | Error accessing https://www.instagram.com, response code: 302 55 | Error accessing https://www.instagram.com, response code: 302 56 | Error accessing https://www.instagram.com, response code: 302 57 | Error accessing https://www.instagram.com, response code: 302 58 | Error accessing https://www.instagram.com, response code: 302 59 | Error accessing https://www.instagram.com, response code: 302 60 | Error accessing https://www.instagram.com, response code: 302 61 | Error accessing https://www.instagram.com, response code: 302 62 | Error accessing https://www.instagram.com, response code: 302 63 | Error accessing https://www.instagram.com, response code: 302 64 | Error accessing https://www.instagram.com, response code: 302 65 | Error accessing https://www.instagram.com, response code: 302 66 | Error accessing https://www.instagram.com, response code: 302 67 | Error accessing https://www.instagram.com, response code: 302 68 | Error accessing https://www.instagram.com, response code: 302 69 | Error accessing https://www.instagram.com, response code: 302 70 | Error accessing https://www.instagram.com, response code: 302 71 | Error accessing https://www.instagram.com, response code: 302 72 | Error accessing https://www.instagram.com, response code: 302 73 | Error accessing https://www.instagram.com, response code: 302 74 | Error accessing https://www.instagram.com, response code: 302 75 | Error accessing https://www.instagram.com, response code: 302 76 | Error accessing https://www.instagram.com, response code: 302 77 | Error accessing https://www.instagram.com, response code: 302 78 | Error accessing https://www.instagram.com, response code: 302 79 | Error accessing https://www.instagram.com, response code: 302 80 | Error accessing https://www.instagram.com, response code: 302 81 | Error accessing https://www.instagram.com, response code: 302 82 | Error accessing https://www.instagram.com, response code: 302 83 | Error accessing https://www.instagram.com, response code: 302 84 | Error accessing https://www.instagram.com, response code: 302 85 | Error accessing https://www.instagram.com, response code: 302 86 | Error accessing https://www.instagram.com, response code: 302 87 | Error accessing https://www.instagram.com, response code: 302 88 | Error accessing https://www.instagram.com, response code: 302 89 | Error accessing https://www.instagram.com, response code: 302 90 | Error accessing https://www.instagram.com, response code: 302 91 | Error accessing https://www.instagram.com, response code: 302 92 | Error accessing https://www.instagram.com, response code: 302 93 | Error accessing https://www.instagram.com, response code: 302 94 | Error accessing https://www.instagram.com, response code: 302 95 | Error accessing https://www.instagram.com, response code: 302 96 | Error accessing https://www.instagram.com, response code: 302 97 | Error accessing https://www.instagram.com, response code: 302 98 | Error accessing https://www.instagram.com, response code: 302 99 | Error accessing https://www.instagram.com, response code: 302 100 | Error accessing https://www.instagram.com, response code: 302 101 | Error accessing https://www.instagram.com, response code: 302 102 | Error accessing https://www.instagram.com, response code: 302 103 | Error accessing https://www.instagram.com, response code: 302 104 | Error accessing https://www.instagram.com, response code: 302 105 | Error accessing https://www.instagram.com, response code: 302 106 | Error accessing https://www.instagram.com, response code: 302 107 | Error accessing https://www.instagram.com, response code: 302 108 | Error accessing https://www.instagram.com, response code: 302 109 | Error accessing https://www.instagram.com, response code: 302 110 | Error accessing https://www.instagram.com, response code: 302 111 | Error accessing https://www.instagram.com, response code: 302 112 | Error accessing https://www.instagram.com, response code: 302 113 | Error accessing https://www.instagram.com, response code: 302 114 | Error accessing https://www.instagram.com, response code: 302 115 | Error accessing https://www.instagram.com, response code: 302 116 | Error accessing https://www.instagram.com, response code: 302 117 | Error accessing https://www.instagram.com, response code: 302 118 | Error accessing https://www.instagram.com, response code: 302 119 | Error accessing https://www.instagram.com, response code: 302 120 | Error accessing https://www.instagram.com, response code: 302 121 | Error accessing https://www.instagram.com, response code: 302 122 | Error accessing https://www.instagram.com, response code: 302 123 | Error accessing https://www.instagram.com, response code: 302 124 | Error accessing https://www.instagram.com, response code: 302 125 | Error accessing https://www.instagram.com, response code: 302 126 | Error accessing https://www.instagram.com, response code: 302 127 | Error accessing https://www.instagram.com, response code: 302 128 | Error accessing https://www.instagram.com, response code: 302 129 | Error accessing https://www.instagram.com, response code: 302 130 | Error accessing https://www.instagram.com, response code: 302 131 | Error accessing https://www.instagram.com, response code: 302 132 | Error accessing https://www.instagram.com, response code: 302 133 | Error accessing https://www.instagram.com, response code: 302 134 | Error accessing https://www.instagram.com, response code: 302 135 | Error accessing https://www.instagram.com, response code: 302 136 | Error accessing https://www.instagram.com, response code: 302 137 | Error accessing https://www.instagram.com, response code: 302 138 | Error accessing https://www.instagram.com, response code: 302 139 | Error accessing https://www.instagram.com, response code: 302 140 | Error accessing https://www.instagram.com, response code: 302 141 | Error accessing https://www.instagram.com, response code: 302 142 | Error accessing https://www.instagram.com, response code: 302 143 | Error accessing https://www.instagram.com, response code: 302 144 | Error accessing https://www.instagram.com, response code: 302 145 | Error accessing https://www.instagram.com, response code: 302 146 | Error accessing https://www.instagram.com, response code: 302 147 | Error accessing https://www.instagram.com, response code: 302 148 | Error accessing https://www.instagram.com, response code: 302 149 | Error accessing https://www.instagram.com, response code: 302 150 | Error accessing https://www.instagram.com, response code: 302 151 | Error accessing https://www.instagram.com, response code: 302 152 | Error accessing https://www.instagram.com, response code: 302 153 | Error accessing https://www.instagram.com, response code: 302 154 | Error accessing https://www.instagram.com, response code: 302 155 | Error accessing https://www.instagram.com, response code: 302 156 | Error accessing https://www.instagram.com, response code: 302 157 | Error accessing https://www.instagram.com, response code: 302 158 | Error accessing https://www.instagram.com, response code: 302 159 | Error accessing https://www.instagram.com, response code: 302 160 | Error accessing https://www.instagram.com, response code: 302 161 | Error accessing https://www.instagram.com, response code: 302 162 | Error accessing https://www.instagram.com, response code: 302 163 | Error accessing https://www.instagram.com, response code: 302 164 | Error accessing https://www.instagram.com, response code: 302 165 | Error accessing https://www.instagram.com, response code: 302 166 | Error accessing https://www.instagram.com, response code: 302 167 | Error accessing https://www.instagram.com, response code: 302 168 | Error accessing https://www.instagram.com, response code: 302 169 | Error accessing https://www.instagram.com, response code: 302 170 | Error accessing https://www.instagram.com, response code: 302 171 | Error accessing https://www.instagram.com, response code: 302 172 | Error accessing https://www.instagram.com, response code: 302 173 | Error accessing https://www.instagram.com, response code: 302 174 | Error accessing https://www.instagram.com, response code: 302 175 | Error accessing https://www.instagram.com, response code: 302 176 | Error accessing https://www.instagram.com, response code: 302 177 | Error accessing https://www.instagram.com, response code: 302 178 | Error accessing https://www.instagram.com, response code: 302 179 | Error accessing https://www.instagram.com, response code: 302 180 | Error accessing https://www.instagram.com, response code: 302 181 | Error accessing https://www.instagram.com, response code: 302 182 | Error accessing https://www.instagram.com, response code: 302 183 | Error accessing https://www.instagram.com, response code: 302 184 | Error accessing https://www.instagram.com, response code: 302 185 | Error accessing https://www.instagram.com, response code: 302 186 | Error accessing https://www.instagram.com, response code: 302 187 | Error accessing https://www.instagram.com, response code: 302 188 | Error accessing https://www.instagram.com, response code: 302 189 | Error accessing https://www.instagram.com, response code: 302 190 | Error accessing https://www.instagram.com, response code: 302 191 | Error accessing https://www.instagram.com, response code: 302 192 | Error accessing https://www.instagram.com, response code: 302 193 | Error accessing https://www.instagram.com, response code: 302 194 | Error accessing https://www.instagram.com, response code: 302 195 | Error accessing https://www.instagram.com, response code: 302 196 | Error accessing https://www.instagram.com, response code: 302 197 | Error accessing https://www.instagram.com, response code: 302 198 | Error accessing https://www.instagram.com, response code: 302 199 | Error accessing https://www.instagram.com, response code: 302 200 | Error accessing https://www.instagram.com, response code: 302 201 | Error accessing https://www.instagram.com, response code: 302 202 | Error accessing https://www.instagram.com, response code: 302 203 | Error accessing https://www.instagram.com, response code: 302 204 | Error accessing https://www.instagram.com, response code: 302 205 | Error accessing https://www.instagram.com, response code: 302 206 | Error accessing https://www.instagram.com, response code: 302 207 | Error accessing https://www.instagram.com, response code: 302 208 | Error accessing https://www.instagram.com, response code: 302 209 | Error accessing https://www.instagram.com, response code: 302 210 | Error accessing https://www.instagram.com, response code: 302 211 | Error accessing https://www.instagram.com, response code: 302 212 | Error accessing https://www.instagram.com, response code: 302 213 | Error accessing https://www.instagram.com, response code: 302 214 | Error accessing https://www.instagram.com, response code: 302 215 | Error accessing https://www.instagram.com, response code: 302 216 | Error accessing https://www.instagram.com, response code: 302 217 | Error accessing https://www.instagram.com, response code: 302 218 | Error accessing https://www.instagram.com, response code: 302 219 | Error accessing https://www.instagram.com, response code: 302 220 | Error accessing https://www.instagram.com, response code: 302 221 | Error accessing https://www.instagram.com, response code: 302 222 | Error accessing https://www.instagram.com, response code: 302 223 | Error accessing https://www.instagram.com, response code: 302 224 | Error accessing https://www.instagram.com, response code: 302 225 | Error accessing https://www.instagram.com, response code: 302 226 | Error accessing https://www.instagram.com, response code: 302 227 | Error accessing https://www.instagram.com, response code: 302 228 | Error accessing https://www.instagram.com, response code: 302 229 | Error accessing https://www.instagram.com, response code: 302 230 | Error accessing https://www.instagram.com, response code: 302 231 | Error accessing https://www.instagram.com, response code: 302 232 | Error accessing https://www.instagram.com, response code: 302 233 | Error accessing https://www.instagram.com, response code: 302 234 | Error accessing https://www.instagram.com, response code: 302 235 | Error accessing https://www.instagram.com, response code: 302 236 | Error accessing https://www.instagram.com, response code: 302 237 | Error accessing https://www.instagram.com, response code: 302 238 | Error accessing https://www.instagram.com, response code: 302 239 | Error accessing https://www.instagram.com, response code: 302 240 | Error accessing https://www.instagram.com, response code: 302 241 | Error accessing https://www.instagram.com, response code: 302 242 | Error accessing https://www.instagram.com, response code: 302 243 | Error accessing https://www.instagram.com, response code: 302 244 | Error accessing https://www.instagram.com, response code: 302 245 | Error accessing https://www.instagram.com, response code: 302 246 | Error accessing https://www.instagram.com, response code: 302 247 | Error accessing https://www.instagram.com, response code: 302 248 | Error accessing https://www.instagram.com, response code: 302 249 | Error accessing https://www.instagram.com, response code: 302 250 | Error accessing https://www.instagram.com, response code: 302 251 | Error accessing https://www.instagram.com, response code: 302 252 | Error accessing https://www.instagram.com, response code: 302 253 | Error accessing https://www.instagram.com, response code: 302 254 | Error accessing https://www.instagram.com, response code: 302 255 | Error accessing https://www.instagram.com, response code: 302 256 | Error accessing https://www.instagram.com, response code: 302 257 | Error accessing https://www.instagram.com, response code: 302 258 | Error accessing https://www.instagram.com, response code: 302 259 | Error accessing https://www.instagram.com, response code: 302 260 | Error accessing https://www.instagram.com, response code: 302 261 | Error accessing https://www.instagram.com, response code: 302 262 | Error accessing https://www.instagram.com, response code: 302 263 | Error accessing https://www.instagram.com, response code: 302 264 | Error accessing https://www.instagram.com, response code: 302 265 | Error accessing https://www.instagram.com, response code: 302 266 | Error accessing https://www.instagram.com, response code: 302 267 | Error accessing https://www.instagram.com, response code: 302 268 | Error accessing https://www.instagram.com, response code: 302 269 | Error accessing https://www.instagram.com, response code: 302 270 | Error accessing https://www.instagram.com, response code: 302 271 | Error accessing https://www.instagram.com, response code: 302 272 | Error accessing https://www.instagram.com, response code: 302 273 | Error accessing https://www.instagram.com, response code: 302 274 | Error accessing https://www.instagram.com, response code: 302 275 | Error accessing https://www.instagram.com, response code: 302 276 | Error accessing https://www.instagram.com, response code: 302 277 | Error accessing https://www.instagram.com, response code: 302 278 | Error accessing https://www.instagram.com, response code: 302 279 | Error accessing https://www.instagram.com, response code: 302 280 | Error accessing https://www.instagram.com, response code: 302 281 | Error accessing https://www.instagram.com, response code: 302 282 | Error accessing https://www.instagram.com, response code: 302 283 | Error accessing https://www.instagram.com, response code: 302 284 | Error accessing https://www.instagram.com, response code: 302 285 | Error accessing https://www.instagram.com, response code: 302 286 | Error accessing https://www.instagram.com, response code: 302 287 | Error accessing https://www.instagram.com, response code: 302 288 | Error accessing https://www.instagram.com, response code: 302 289 | Error accessing https://www.instagram.com, response code: 302 290 | Error accessing https://www.instagram.com, response code: 302 291 | Error accessing https://www.instagram.com, response code: 302 292 | Error accessing https://www.instagram.com, response code: 302 293 | Error accessing https://www.instagram.com, response code: 302 294 | Error accessing https://www.instagram.com, response code: 302 295 | Error accessing https://www.instagram.com, response code: 302 296 | Error accessing https://www.instagram.com, response code: 302 297 | Error accessing https://www.instagram.com, response code: 302 298 | Error accessing https://www.instagram.com, response code: 302 299 | Error accessing https://www.instagram.com, response code: 302 300 | Error accessing https://www.instagram.com, response code: 302 301 | Error accessing https://www.instagram.com, response code: 302 302 | Error accessing https://www.instagram.com, response code: 302 303 | Error accessing https://www.instagram.com, response code: 302 304 | Error accessing https://www.instagram.com, response code: 302 305 | Error accessing https://www.instagram.com, response code: 302 306 | Error accessing https://www.instagram.com, response code: 302 307 | Error accessing https://www.instagram.com, response code: 302 308 | Error accessing https://www.instagram.com, response code: 302 309 | Error accessing https://www.instagram.com, response code: 302 310 | Error accessing https://www.instagram.com, response code: 302 311 | Error accessing https://www.instagram.com, response code: 302 312 | Error accessing https://www.instagram.com, response code: 302 313 | Error accessing https://www.instagram.com, response code: 302 314 | Error accessing https://www.instagram.com, response code: 302 315 | Error accessing https://www.instagram.com, response code: 302 316 | Error accessing https://www.instagram.com, response code: 302 317 | Error accessing https://www.instagram.com, response code: 302 318 | Error accessing https://www.instagram.com, response code: 302 319 | Error accessing https://www.instagram.com, response code: 302 320 | Error accessing https://www.instagram.com, response code: 302 321 | Error accessing https://www.instagram.com, response code: 302 322 | Error accessing https://www.instagram.com, response code: 302 323 | Error accessing https://www.instagram.com, response code: 302 324 | Error accessing https://www.instagram.com, response code: 302 325 | Error accessing https://www.instagram.com, response code: 302 326 | Error accessing https://www.instagram.com, response code: 302 327 | Error accessing https://www.instagram.com, response code: 302 328 | Error accessing https://www.instagram.com, response code: 302 329 | Error accessing https://www.instagram.com, response code: 302 330 | Error accessing https://www.instagram.com, response code: 302 331 | Error accessing https://www.instagram.com, response code: 302 332 | Error accessing https://www.instagram.com, response code: 302 333 | Error accessing https://www.instagram.com, response code: 302 334 | Error accessing https://www.instagram.com, response code: 302 335 | Error accessing https://www.instagram.com, response code: 302 336 | Error accessing https://www.instagram.com, response code: 302 337 | Error accessing https://www.instagram.com, response code: 302 338 | Error accessing https://www.instagram.com, response code: 302 339 | Error accessing https://www.instagram.com, response code: 302 340 | Error accessing https://www.instagram.com, response code: 302 341 | Error accessing https://www.instagram.com, response code: 302 342 | Error accessing https://www.instagram.com, response code: 302 343 | Error accessing https://www.instagram.com, response code: 302 344 | Error accessing https://www.instagram.com, response code: 302 345 | Error accessing https://www.instagram.com, response code: 302 346 | Error accessing https://www.instagram.com, response code: 302 347 | Error accessing https://www.instagram.com, response code: 302 348 | Error accessing https://www.instagram.com, response code: 302 349 | Error accessing https://www.instagram.com, response code: 302 350 | Error accessing https://www.instagram.com, response code: 302 351 | Error accessing https://www.instagram.com, response code: 302 352 | Error accessing https://www.instagram.com, response code: 302 353 | Error accessing https://www.instagram.com, response code: 302 354 | Error accessing https://www.instagram.com, response code: 302 355 | Error accessing https://www.instagram.com, response code: 302 356 | Error accessing https://www.instagram.com, response code: 302 357 | Error accessing https://www.instagram.com, response code: 302 358 | Error accessing https://www.instagram.com, response code: 302 359 | Error accessing https://www.instagram.com, response code: 302 360 | Error accessing https://www.instagram.com, response code: 302 361 | Error accessing https://www.instagram.com, response code: 302 362 | Error accessing https://www.instagram.com, response code: 302 363 | Error accessing https://www.instagram.com, response code: 302 364 | Error accessing https://www.instagram.com, response code: 302 365 | Error accessing https://www.instagram.com, response code: 302 366 | Error accessing https://www.instagram.com, response code: 302 367 | Error accessing https://www.instagram.com, response code: 302 368 | Error accessing https://www.instagram.com, response code: 302 369 | Error accessing https://www.instagram.com, response code: 302 370 | Error accessing https://www.instagram.com, response code: 302 371 | Error accessing https://www.instagram.com, response code: 302 372 | Error accessing https://www.instagram.com, response code: 302 373 | Error accessing https://www.instagram.com, response code: 302 374 | Error accessing https://www.instagram.com, response code: 302 375 | Error accessing https://www.instagram.com, response code: 302 376 | Error accessing https://www.instagram.com, response code: 302 377 | Error accessing https://www.instagram.com, response code: 302 378 | Error accessing https://www.instagram.com, response code: 302 379 | Error accessing https://www.instagram.com, response code: 302 380 | Error accessing https://www.instagram.com, response code: 302 381 | Error accessing https://www.instagram.com, response code: 302 382 | Error accessing https://www.instagram.com, response code: 302 383 | Error accessing https://www.instagram.com, response code: 302 384 | Error accessing https://www.instagram.com, response code: 302 385 | Error accessing https://www.instagram.com, response code: 302 386 | Error accessing https://www.instagram.com, response code: 302 387 | Error accessing https://www.instagram.com, response code: 302 388 | Error accessing https://www.instagram.com, response code: 302 389 | Error accessing https://www.instagram.com, response code: 302 390 | Error accessing https://www.instagram.com, response code: 302 391 | Error accessing https://www.instagram.com, response code: 302 392 | Error accessing https://www.instagram.com, response code: 302 393 | Error accessing https://www.instagram.com, response code: 302 394 | Error accessing https://www.instagram.com, response code: 302 395 | Error accessing https://www.instagram.com, response code: 302 396 | Error accessing https://www.instagram.com, response code: 302 397 | Error accessing https://www.instagram.com, response code: 302 398 | Error accessing https://www.instagram.com, response code: 302 399 | Error accessing https://www.instagram.com, response code: 302 400 | Error accessing https://www.instagram.com, response code: 302 401 | Error accessing https://www.instagram.com, response code: 302 402 | Error accessing https://www.instagram.com, response code: 302 403 | Error accessing https://www.instagram.com, response code: 302 404 | Error accessing https://www.instagram.com, response code: 302 405 | Error accessing https://www.instagram.com, response code: 302 406 | Error accessing https://www.instagram.com, response code: 302 407 | Error accessing https://www.instagram.com, response code: 302 408 | Error accessing https://www.instagram.com, response code: 302 409 | Error accessing https://www.instagram.com, response code: 302 410 | Error accessing https://www.instagram.com, response code: 302 411 | Error accessing https://www.instagram.com, response code: 302 412 | Error accessing https://www.instagram.com, response code: 302 413 | Error accessing https://www.instagram.com, response code: 302 414 | Error accessing https://www.instagram.com, response code: 302 415 | Error accessing https://www.instagram.com, response code: 302 416 | Error accessing https://www.instagram.com, response code: 302 417 | Error accessing https://www.instagram.com, response code: 302 418 | Error accessing https://www.instagram.com, response code: 302 419 | Error accessing https://www.instagram.com, response code: 302 420 | Error accessing https://www.instagram.com, response code: 302 421 | Error accessing https://www.instagram.com, response code: 302 422 | Error accessing https://www.instagram.com, response code: 302 423 | Error accessing https://www.instagram.com, response code: 302 424 | Error accessing https://www.instagram.com, response code: 302 425 | Error accessing https://www.instagram.com, response code: 302 426 | Error accessing https://www.instagram.com, response code: 302 427 | Error accessing https://www.instagram.com, response code: 302 428 | Error accessing https://www.instagram.com, response code: 302 429 | Error accessing https://www.instagram.com, response code: 302 430 | Error accessing https://www.instagram.com, response code: 302 431 | Error accessing https://www.instagram.com, response code: 302 432 | Error accessing https://www.instagram.com, response code: 302 433 | Error accessing https://www.instagram.com, response code: 302 434 | Error accessing https://www.instagram.com, response code: 302 435 | Error accessing https://www.instagram.com, response code: 302 436 | Error accessing https://www.instagram.com, response code: 302 437 | Error accessing https://www.instagram.com, response code: 302 438 | Error accessing https://www.instagram.com, response code: 302 439 | Error accessing https://www.instagram.com, response code: 302 440 | Error accessing https://www.instagram.com, response code: 302 441 | Error accessing https://www.instagram.com, response code: 302 442 | Error accessing https://www.instagram.com, response code: 302 443 | Error accessing https://www.instagram.com, response code: 302 444 | Error accessing https://www.instagram.com, response code: 302 445 | Error accessing https://www.instagram.com, response code: 302 446 | Error accessing https://www.instagram.com, response code: 302 447 | Error accessing https://www.instagram.com, response code: 302 448 | Error accessing https://www.instagram.com, response code: 302 449 | Error accessing https://www.instagram.com, response code: 302 450 | Error accessing https://www.instagram.com, response code: 302 451 | Error accessing https://www.instagram.com, response code: 302 452 | Error accessing https://www.instagram.com, response code: 302 453 | Error accessing https://www.instagram.com, response code: 302 454 | Error accessing https://www.instagram.com, response code: 302 455 | Error accessing https://www.instagram.com, response code: 302 456 | Error accessing https://www.instagram.com, response code: 302 457 | Error accessing https://www.instagram.com, response code: 302 458 | Error accessing https://www.instagram.com, response code: 302 459 | Error accessing https://www.instagram.com, response code: 302 460 | Error accessing https://www.instagram.com, response code: 302 461 | Error accessing https://www.instagram.com, response code: 302 462 | Error accessing https://www.instagram.com, response code: 302 463 | Error accessing https://www.instagram.com, response code: 302 464 | Error accessing https://www.instagram.com, response code: 302 465 | Error accessing https://www.instagram.com, response code: 302 466 | Error accessing https://www.instagram.com, response code: 302 467 | Error accessing https://www.instagram.com, response code: 302 468 | Error accessing https://www.instagram.com, response code: 302 469 | Error accessing https://www.instagram.com, response code: 302 470 | Error accessing https://www.instagram.com, response code: 302 471 | Error accessing https://www.instagram.com, response code: 302 472 | Error accessing https://www.instagram.com, response code: 302 473 | Error accessing https://www.instagram.com, response code: 302 474 | Error accessing https://www.instagram.com, response code: 302 475 | Error accessing https://www.instagram.com, response code: 302 476 | Error accessing https://www.instagram.com, response code: 302 477 | Error accessing https://www.instagram.com, response code: 302 478 | Error accessing https://www.instagram.com, response code: 302 479 | Error accessing https://www.instagram.com, response code: 302 480 | Error accessing https://www.instagram.com, response code: 302 481 | Error accessing https://www.instagram.com, response code: 302 482 | Error accessing https://www.instagram.com, response code: 302 483 | Error accessing https://www.instagram.com, response code: 302 484 | Error accessing https://www.instagram.com, response code: 302 485 | Error accessing https://www.instagram.com, response code: 302 486 | Error accessing https://www.instagram.com, response code: 302 487 | Error accessing https://www.instagram.com, response code: 302 488 | Error accessing https://www.instagram.com, response code: 302 489 | Error accessing https://www.instagram.com, response code: 302 490 | Error accessing https://www.instagram.com, response code: 302 491 | Error accessing https://www.instagram.com, response code: 302 492 | Error accessing https://www.instagram.com, response code: 302 493 | Error accessing https://www.instagram.com, response code: 302 494 | Error accessing https://www.instagram.com, response code: 302 495 | Error accessing https://www.instagram.com, response code: 302 496 | Error accessing https://www.instagram.com, response code: 302 497 | Error accessing https://www.instagram.com, response code: 302 498 | Error accessing https://www.instagram.com, response code: 302 499 | Error accessing https://www.instagram.com, response code: 302 500 | Error accessing https://www.instagram.com, response code: 302 501 | Error accessing https://www.instagram.com, response code: 302 502 | Error accessing https://www.instagram.com, response code: 302 503 | Error accessing https://www.instagram.com, response code: 302 504 | Error accessing https://www.instagram.com, response code: 302 505 | Error accessing https://www.instagram.com, response code: 302 506 | Error accessing https://www.instagram.com, response code: 302 507 | Error accessing https://www.instagram.com, response code: 302 508 | Error accessing https://www.instagram.com, response code: 302 509 | Error accessing https://www.instagram.com, response code: 302 510 | Error accessing https://www.instagram.com, response code: 302 511 | Error accessing https://www.instagram.com, response code: 302 512 | Error accessing https://www.instagram.com, response code: 302 513 | Error accessing https://www.instagram.com, response code: 302 514 | Error accessing https://www.instagram.com, response code: 302 515 | Error accessing https://www.instagram.com, response code: 302 516 | Error accessing https://www.instagram.com, response code: 302 517 | Error accessing https://www.instagram.com, response code: 302 518 | Error accessing https://www.instagram.com, response code: 302 519 | Error accessing https://www.instagram.com, response code: 302 520 | Error accessing https://www.instagram.com, response code: 302 521 | Error accessing https://www.instagram.com, response code: 302 522 | Error accessing https://www.instagram.com, response code: 302 523 | Error accessing https://www.instagram.com, response code: 302 524 | Error accessing https://www.instagram.com, response code: 302 525 | Error accessing https://www.instagram.com, response code: 302 526 | Error accessing https://www.instagram.com, response code: 302 527 | Error accessing https://www.instagram.com, response code: 302 528 | Error accessing https://www.instagram.com, response code: 302 529 | Error accessing https://www.instagram.com, response code: 302 530 | Error accessing https://www.instagram.com, response code: 302 531 | Error accessing https://www.instagram.com, response code: 302 532 | Error accessing https://www.instagram.com, response code: 302 533 | Error accessing https://www.instagram.com, response code: 302 534 | Error accessing https://www.instagram.com, response code: 302 535 | Error accessing https://www.instagram.com, response code: 302 536 | Error accessing https://www.instagram.com, response code: 302 537 | Error accessing https://www.instagram.com, response code: 302 538 | Error accessing https://www.instagram.com, response code: 302 539 | Error accessing https://www.instagram.com, response code: 302 540 | Error accessing https://www.instagram.com, response code: 302 541 | Error accessing https://www.instagram.com, response code: 302 542 | Error accessing https://www.instagram.com, response code: 302 543 | Error accessing https://www.instagram.com, response code: 302 544 | Error accessing https://www.instagram.com, response code: 302 545 | Error accessing https://www.instagram.com, response code: 302 546 | Error accessing https://www.instagram.com, response code: 302 547 | Error accessing https://www.instagram.com, response code: 302 548 | Error accessing https://www.instagram.com, response code: 302 549 | Error accessing https://www.instagram.com, response code: 302 550 | Error accessing https://www.instagram.com, response code: 302 551 | Error accessing https://www.instagram.com, response code: 302 552 | Error accessing https://www.instagram.com, response code: 302 553 | Error accessing https://www.instagram.com, response code: 302 554 | Error accessing https://www.instagram.com, response code: 302 555 | Error accessing https://www.instagram.com, response code: 302 556 | Error accessing https://www.instagram.com, response code: 302 557 | Error accessing https://www.instagram.com, response code: 302 558 | Error accessing https://www.instagram.com, response code: 302 559 | Error accessing https://www.instagram.com, response code: 302 560 | Error accessing https://www.instagram.com, response code: 302 561 | Error accessing https://www.instagram.com, response code: 302 562 | Error accessing https://www.instagram.com, response code: 302 563 | Error accessing https://www.instagram.com, response code: 302 564 | Error accessing https://www.instagram.com, response code: 302 565 | Error accessing https://www.instagram.com, response code: 302 566 | Error accessing https://www.instagram.com, response code: 302 567 | Error accessing https://www.instagram.com, response code: 302 568 | Error accessing https://www.instagram.com, response code: 302 569 | Error accessing https://www.instagram.com, response code: 302 570 | Error accessing https://www.instagram.com, response code: 302 571 | Error accessing https://www.instagram.com, response code: 302 572 | Error accessing https://www.instagram.com, response code: 302 573 | Error accessing https://www.instagram.com, response code: 302 574 | Error accessing https://www.instagram.com, response code: 302 575 | Error accessing https://www.instagram.com, response code: 302 576 | Error accessing https://www.instagram.com, response code: 302 577 | Error accessing https://www.instagram.com, response code: 302 578 | Error accessing https://www.instagram.com, response code: 302 579 | Error accessing https://www.instagram.com, response code: 302 580 | Error accessing https://www.instagram.com, response code: 302 581 | Error accessing https://www.instagram.com, response code: 302 582 | Error accessing https://www.instagram.com, response code: 302 583 | Error accessing https://www.instagram.com, response code: 302 584 | Error accessing https://www.instagram.com, response code: 302 585 | Error accessing https://www.instagram.com, response code: 302 586 | Error accessing https://www.instagram.com, response code: 302 587 | Error accessing https://www.instagram.com, response code: 302 588 | Error accessing https://www.instagram.com, response code: 302 589 | Error accessing https://www.instagram.com, response code: 302 590 | Error accessing https://www.instagram.com, response code: 302 591 | Error accessing https://www.instagram.com, response code: 302 592 | Error accessing https://www.instagram.com, response code: 302 593 | Error accessing https://www.instagram.com, response code: 302 594 | Error accessing https://www.instagram.com, response code: 302 595 | Error accessing https://www.instagram.com, response code: 302 596 | Error accessing https://www.instagram.com, response code: 302 597 | Error accessing https://www.instagram.com, response code: 302 598 | Error accessing https://www.instagram.com, response code: 302 599 | Error accessing https://www.instagram.com, response code: 302 600 | Error accessing https://www.instagram.com, response code: 302 601 | Error accessing https://www.instagram.com, response code: 302 602 | Error accessing https://www.instagram.com, response code: 302 603 | Error accessing https://www.instagram.com, response code: 302 604 | Error accessing https://www.instagram.com, response code: 302 605 | Error accessing https://www.instagram.com, response code: 302 606 | Error accessing https://www.instagram.com, response code: 302 607 | Error accessing https://www.instagram.com, response code: 302 608 | Error accessing https://www.instagram.com, response code: 302 609 | Error accessing https://www.instagram.com, response code: 302 610 | Error accessing https://www.instagram.com, response code: 302 611 | Error accessing https://www.instagram.com, response code: 302 612 | Error accessing https://www.instagram.com, response code: 302 613 | Error accessing https://www.instagram.com, response code: 302 614 | Error accessing https://www.instagram.com, response code: 302 615 | Error accessing https://www.instagram.com, response code: 302 616 | Error accessing https://www.instagram.com, response code: 302 617 | Error accessing https://www.instagram.com, response code: 302 618 | Error accessing https://www.instagram.com, response code: 302 619 | Error accessing https://www.instagram.com, response code: 302 620 | Error accessing https://www.instagram.com, response code: 302 621 | Error accessing https://www.instagram.com, response code: 302 622 | Error accessing https://www.instagram.com, response code: 302 623 | Error accessing https://www.instagram.com, response code: 302 624 | Error accessing https://www.instagram.com, response code: 302 625 | Error accessing https://www.instagram.com, response code: 302 626 | Error accessing https://www.instagram.com, response code: 302 627 | Error accessing https://www.instagram.com, response code: 302 628 | Error accessing https://www.instagram.com, response code: 302 629 | Error accessing https://www.instagram.com, response code: 302 630 | Error accessing https://www.instagram.com, response code: 302 631 | Error accessing https://www.instagram.com, response code: 302 632 | Error accessing https://www.instagram.com, response code: 302 633 | Error accessing https://www.instagram.com, response code: 302 634 | Error accessing https://www.instagram.com, response code: 302 635 | Error accessing https://www.instagram.com, response code: 302 636 | Error accessing https://www.instagram.com, response code: 302 637 | Error accessing https://www.instagram.com, response code: 302 638 | Error accessing https://www.instagram.com, response code: 302 639 | Error accessing https://www.instagram.com, response code: 302 640 | Error accessing https://www.instagram.com, response code: 302 641 | Error accessing https://www.instagram.com, response code: 302 642 | Error accessing https://www.instagram.com, response code: 302 643 | Error accessing https://www.instagram.com, response code: 302 644 | Error accessing https://www.instagram.com, response code: 302 645 | Error accessing https://www.instagram.com, response code: 302 646 | Error accessing https://www.instagram.com, response code: 302 647 | Error accessing https://www.instagram.com, response code: 302 648 | Error accessing https://www.instagram.com, response code: 302 649 | Error accessing https://www.instagram.com, response code: 302 650 | Error accessing https://www.instagram.com, response code: 302 651 | Error accessing https://www.instagram.com, response code: 302 652 | Error accessing https://www.instagram.com, response code: 302 653 | Error accessing https://www.instagram.com, response code: 302 654 | Error accessing https://www.instagram.com, response code: 302 655 | Error accessing https://www.instagram.com, response code: 302 656 | Error accessing https://www.instagram.com, response code: 302 657 | Error accessing https://www.instagram.com, response code: 302 658 | Error accessing https://www.instagram.com, response code: 302 659 | Error accessing https://www.instagram.com, response code: 302 660 | Error accessing https://www.instagram.com, response code: 302 661 | Error accessing https://www.instagram.com, response code: 302 662 | Error accessing https://www.instagram.com, response code: 302 663 | Error accessing https://www.instagram.com, response code: 302 664 | Error accessing https://www.instagram.com, response code: 302 665 | Error accessing https://www.instagram.com, response code: 302 666 | Error accessing https://www.instagram.com, response code: 302 667 | Error accessing https://www.instagram.com, response code: 302 668 | Error accessing https://www.instagram.com, response code: 302 669 | Error accessing https://www.instagram.com, response code: 302 670 | Error accessing https://www.instagram.com, response code: 302 671 | Error accessing https://www.instagram.com, response code: 302 672 | Error accessing https://www.instagram.com, response code: 302 673 | Error accessing https://www.instagram.com, response code: 302 674 | Error accessing https://www.instagram.com, response code: 302 675 | Error accessing https://www.instagram.com, response code: 302 676 | Error accessing https://www.instagram.com, response code: 302 677 | Error accessing https://www.instagram.com, response code: 302 678 | Error accessing https://www.instagram.com, response code: 302 679 | Error accessing https://www.instagram.com, response code: 302 680 | Error accessing https://www.instagram.com, response code: 302 681 | Error accessing https://www.instagram.com, response code: 302 682 | Error accessing https://www.instagram.com, response code: 302 683 | Error accessing https://www.instagram.com, response code: 302 684 | Error accessing https://www.instagram.com, response code: 302 685 | Error accessing https://www.instagram.com, response code: 302 686 | Error accessing https://www.instagram.com, response code: 302 687 | Error accessing https://www.instagram.com, response code: 302 688 | Error accessing https://www.instagram.com, response code: 302 689 | Error accessing https://www.instagram.com, response code: 302 690 | Error accessing https://www.instagram.com, response code: 302 691 | Error accessing https://www.instagram.com, response code: 302 692 | Error accessing https://www.instagram.com, response code: 302 693 | Error accessing https://www.instagram.com, response code: 302 694 | Error accessing https://www.instagram.com, response code: 302 695 | Error accessing https://www.instagram.com, response code: 302 696 | Error accessing https://www.instagram.com, response code: 302 697 | Error accessing https://www.instagram.com, response code: 302 698 | Error accessing https://www.instagram.com, response code: 302 699 | Error accessing https://www.instagram.com, response code: 302 700 | Error accessing https://www.instagram.com, response code: 302 701 | Error accessing https://www.instagram.com, response code: 302 702 | Error accessing https://www.instagram.com, response code: 302 703 | Error accessing https://www.instagram.com, response code: 302 704 | Error accessing https://www.instagram.com, response code: 302 705 | Error accessing https://www.instagram.com, response code: 302 706 | Error accessing https://www.instagram.com, response code: 302 707 | Error accessing https://www.instagram.com, response code: 302 708 | Error accessing https://www.instagram.com, response code: 302 709 | Error accessing https://www.instagram.com, response code: 302 710 | Error accessing https://www.instagram.com, response code: 302 711 | Error accessing https://www.instagram.com, response code: 302 712 | Error accessing https://www.instagram.com, response code: 302 713 | Error accessing https://www.instagram.com, response code: 302 714 | Error accessing https://www.instagram.com, response code: 302 715 | Error accessing https://www.instagram.com, response code: 302 716 | Error accessing https://www.instagram.com, response code: 302 717 | Error accessing https://www.instagram.com, response code: 302 718 | Error accessing https://www.instagram.com, response code: 302 719 | Error accessing https://www.instagram.com, response code: 302 720 | Error accessing https://www.instagram.com, response code: 302 721 | Error accessing https://www.instagram.com, response code: 302 722 | Error accessing https://www.instagram.com, response code: 302 723 | Error accessing https://www.instagram.com, response code: 302 724 | Error accessing https://www.instagram.com, response code: 302 725 | Error accessing https://www.instagram.com, response code: 302 726 | Error accessing https://www.instagram.com, response code: 302 727 | Error accessing https://www.instagram.com, response code: 302 728 | Error accessing https://www.instagram.com, response code: 302 729 | Error accessing https://www.instagram.com, response code: 302 730 | Error accessing https://www.instagram.com, response code: 302 731 | Error accessing https://www.instagram.com, response code: 302 732 | Error accessing https://www.instagram.com, response code: 302 733 | Error accessing https://www.instagram.com, response code: 302 734 | Error accessing https://www.instagram.com, response code: 302 735 | Error accessing https://www.instagram.com, response code: 302 736 | Error accessing https://www.instagram.com, response code: 302 737 | Error accessing https://www.instagram.com, response code: 302 738 | Error accessing https://www.instagram.com, response code: 302 739 | Error accessing https://www.instagram.com, response code: 302 740 | Error accessing https://www.instagram.com, response code: 302 741 | Error accessing https://www.instagram.com, response code: 302 742 | Error accessing https://www.instagram.com, response code: 302 743 | Error accessing https://www.instagram.com, response code: 302 744 | Error accessing https://www.instagram.com, response code: 302 745 | Error accessing https://www.instagram.com, response code: 302 746 | Error accessing https://www.instagram.com, response code: 302 747 | Error accessing https://www.instagram.com, response code: 302 748 | Error accessing https://www.instagram.com, response code: 302 749 | Error accessing https://www.instagram.com, response code: 302 750 | Error accessing https://www.instagram.com, response code: 302 751 | Error accessing https://www.instagram.com, response code: 302 752 | Error accessing https://www.instagram.com, response code: 302 753 | Error accessing https://www.instagram.com, response code: 302 754 | Error accessing https://www.instagram.com, response code: 302 755 | Error accessing https://www.instagram.com, response code: 302 756 | Error accessing https://www.instagram.com, response code: 302 757 | Error accessing https://www.instagram.com, response code: 302 758 | Error accessing https://www.instagram.com, response code: 302 759 | Error accessing https://www.instagram.com, response code: 302 760 | Error accessing https://www.instagram.com, response code: 302 761 | Error accessing https://www.instagram.com, response code: 302 762 | Error accessing https://www.instagram.com, response code: 302 763 | Error accessing https://www.instagram.com, response code: 302 764 | Error accessing https://www.instagram.com, response code: 302 765 | Error accessing https://www.instagram.com, response code: 302 766 | Error accessing https://www.instagram.com, response code: 302 767 | Error accessing https://www.instagram.com, response code: 302 768 | Error accessing https://www.instagram.com, response code: 302 769 | Error accessing https://www.instagram.com, response code: 302 770 | Error accessing https://www.instagram.com, response code: 302 771 | Error accessing https://www.instagram.com, response code: 302 772 | Error accessing https://www.instagram.com, response code: 302 773 | Error accessing https://www.instagram.com, response code: 302 774 | Error accessing https://www.instagram.com, response code: 302 775 | Error accessing https://www.instagram.com, response code: 302 776 | Error accessing https://www.instagram.com, response code: 302 777 | Error accessing https://www.instagram.com, response code: 302 778 | Error accessing https://www.instagram.com, response code: 302 779 | Error accessing https://www.instagram.com, response code: 302 780 | Error accessing https://www.instagram.com, response code: 302 781 | Error accessing https://www.instagram.com, response code: 302 782 | Error accessing https://www.instagram.com, response code: 302 783 | Error accessing https://www.instagram.com, response code: 302 784 | Error accessing https://www.instagram.com, response code: 302 785 | Error accessing https://www.instagram.com, response code: 302 786 | Error accessing https://www.instagram.com, response code: 302 787 | Error accessing https://www.instagram.com, response code: 302 788 | Error accessing https://www.instagram.com, response code: 302 789 | Error accessing https://www.instagram.com, response code: 302 790 | Error accessing https://www.instagram.com, response code: 302 791 | Error accessing https://www.instagram.com, response code: 302 792 | Error accessing https://www.instagram.com, response code: 302 793 | Error accessing https://www.instagram.com, response code: 302 794 | Error accessing https://www.instagram.com, response code: 302 795 | Error accessing https://www.instagram.com, response code: 302 796 | Error accessing https://www.instagram.com, response code: 302 797 | Error accessing https://www.instagram.com, response code: 302 798 | Error accessing https://www.instagram.com, response code: 302 799 | Error accessing https://www.instagram.com, response code: 302 800 | Error accessing https://www.instagram.com, response code: 302 801 | Error accessing https://www.instagram.com, response code: 302 802 | Error accessing https://www.instagram.com, response code: 302 803 | Error accessing https://www.instagram.com, response code: 302 804 | Error accessing https://www.instagram.com, response code: 302 805 | Error accessing https://www.instagram.com, response code: 302 806 | Error accessing https://www.instagram.com, response code: 302 807 | Error accessing https://www.instagram.com, response code: 302 808 | Error accessing https://www.instagram.com, response code: 302 809 | Error accessing https://www.instagram.com, response code: 302 810 | Error accessing https://www.instagram.com, response code: 302 811 | Error accessing https://www.instagram.com, response code: 302 812 | Error accessing https://www.instagram.com, response code: 302 813 | Error accessing https://www.instagram.com, response code: 302 814 | Error accessing https://www.instagram.com, response code: 302 815 | Error accessing https://www.instagram.com, response code: 302 816 | Error accessing https://www.instagram.com, response code: 302 817 | Error accessing https://www.instagram.com, response code: 302 818 | Error accessing https://www.instagram.com, response code: 302 819 | Error accessing https://www.instagram.com, response code: 302 820 | Error accessing https://www.instagram.com, response code: 302 821 | Error accessing https://www.instagram.com, response code: 302 822 | Error accessing https://www.instagram.com, response code: 302 823 | Error accessing https://www.instagram.com, response code: 302 824 | Error accessing https://www.instagram.com, response code: 302 825 | Error accessing https://www.instagram.com, response code: 302 826 | Error accessing https://www.instagram.com, response code: 302 827 | Error accessing https://www.instagram.com, response code: 302 828 | Error accessing https://www.instagram.com, response code: 302 829 | Error accessing https://www.instagram.com, response code: 302 830 | Error accessing https://www.instagram.com, response code: 302 831 | Error accessing https://www.instagram.com, response code: 302 832 | Error accessing https://www.instagram.com, response code: 302 833 | Error accessing https://www.instagram.com, response code: 302 834 | Error accessing https://www.instagram.com, response code: 302 835 | Error accessing https://www.instagram.com, response code: 302 836 | Error accessing https://www.instagram.com, response code: 302 837 | Error accessing https://www.instagram.com, response code: 302 838 | Error accessing https://www.instagram.com, response code: 302 839 | Error accessing https://www.instagram.com, response code: 302 840 | Error accessing https://www.instagram.com, response code: 302 841 | Error accessing https://www.instagram.com, response code: 302 842 | Error accessing https://www.instagram.com, response code: 302 843 | Error accessing https://www.instagram.com, response code: 302 844 | Error accessing https://www.instagram.com, response code: 302 845 | Error accessing https://www.instagram.com, response code: 302 846 | Error accessing https://www.instagram.com, response code: 302 847 | Error accessing https://www.instagram.com, response code: 302 848 | Error accessing https://www.instagram.com, response code: 302 849 | Error accessing https://www.instagram.com, response code: 302 850 | Error accessing https://www.instagram.com, response code: 302 851 | Error accessing https://www.instagram.com, response code: 302 852 | Error accessing https://www.instagram.com, response code: 302 853 | Error accessing https://www.instagram.com, response code: 302 854 | Error accessing https://www.instagram.com, response code: 302 855 | Error accessing https://www.instagram.com, response code: 302 856 | Error accessing https://www.instagram.com, response code: 302 857 | Error accessing https://www.instagram.com, response code: 302 858 | Error accessing https://www.instagram.com, response code: 302 859 | Error accessing https://www.instagram.com, response code: 302 860 | Error accessing https://www.instagram.com, response code: 302 861 | Error accessing https://www.instagram.com, response code: 302 862 | Error accessing https://www.instagram.com, response code: 302 863 | Error accessing https://www.instagram.com, response code: 302 864 | Error accessing https://www.instagram.com, response code: 302 865 | Error accessing https://www.instagram.com, response code: 302 866 | Error accessing https://www.instagram.com, response code: 302 867 | Error accessing https://www.instagram.com, response code: 302 868 | Error accessing https://www.instagram.com, response code: 302 869 | Error accessing https://www.instagram.com, response code: 302 870 | Error accessing https://www.instagram.com, response code: 302 871 | Error accessing https://www.instagram.com, response code: 302 872 | Error accessing https://www.instagram.com, response code: 302 873 | Error accessing https://www.instagram.com, response code: 302 874 | Error accessing https://www.instagram.com, response code: 302 875 | Error accessing https://www.instagram.com, response code: 302 876 | Error accessing https://www.instagram.com, response code: 302 877 | Error accessing https://www.instagram.com, response code: 302 878 | Error accessing https://www.instagram.com, response code: 302 879 | Error accessing https://www.instagram.com, response code: 302 880 | Error accessing https://www.instagram.com, response code: 302 881 | Error accessing https://www.instagram.com, response code: 302 882 | Error accessing https://www.instagram.com, response code: 302 883 | Error accessing https://www.instagram.com, response code: 302 884 | Error accessing https://www.instagram.com, response code: 302 885 | Error accessing https://www.instagram.com, response code: 302 886 | Error accessing https://www.instagram.com, response code: 302 887 | Error accessing https://www.instagram.com, response code: 302 888 | Error accessing https://www.instagram.com, response code: 302 889 | Error accessing https://www.instagram.com, response code: 302 890 | Error accessing https://www.instagram.com, response code: 302 891 | Error accessing https://www.instagram.com, response code: 302 892 | Error accessing https://www.instagram.com, response code: 302 893 | Error accessing https://www.instagram.com, response code: 302 894 | Error accessing https://www.instagram.com, response code: 302 895 | Error accessing https://www.instagram.com, response code: 302 896 | Error accessing https://www.instagram.com, response code: 302 897 | Error accessing https://www.instagram.com, response code: 302 898 | Error accessing https://www.instagram.com, response code: 302 899 | Error accessing https://www.instagram.com, response code: 302 900 | Error accessing https://www.instagram.com, response code: 302 901 | Error accessing https://www.instagram.com, response code: 302 902 | Error accessing https://www.instagram.com, response code: 302 903 | Error accessing https://www.instagram.com, response code: 302 904 | Error accessing https://www.instagram.com, response code: 302 905 | Error accessing https://www.instagram.com, response code: 302 906 | Error accessing https://www.instagram.com, response code: 302 907 | Error accessing https://www.instagram.com, response code: 302 908 | Error accessing https://www.instagram.com, response code: 302 909 | Error accessing https://www.instagram.com, response code: 302 910 | Error accessing https://www.instagram.com, response code: 302 911 | Error accessing https://www.instagram.com, response code: 302 912 | Error accessing https://www.instagram.com, response code: 302 913 | Error accessing https://www.instagram.com, response code: 302 914 | Error accessing https://www.instagram.com, response code: 302 915 | Error accessing https://www.instagram.com, response code: 302 916 | Error accessing https://www.instagram.com, response code: 302 917 | Error accessing https://www.instagram.com, response code: 302 918 | Error accessing https://www.instagram.com, response code: 302 919 | Error accessing https://www.instagram.com, response code: 302 920 | Error accessing https://www.instagram.com, response code: 302 921 | Error accessing https://www.instagram.com, response code: 302 922 | Error accessing https://www.instagram.com, response code: 302 923 | Error accessing https://www.instagram.com, response code: 302 924 | Error accessing https://www.instagram.com, response code: 302 925 | Error accessing https://www.instagram.com, response code: 302 926 | Error accessing https://www.instagram.com, response code: 302 927 | Error accessing https://www.instagram.com, response code: 302 928 | Error accessing https://www.instagram.com, response code: 302 929 | Error accessing https://www.instagram.com, response code: 302 930 | Error accessing https://www.instagram.com, response code: 302 931 | Error accessing https://www.instagram.com, response code: 302 932 | Error accessing https://www.instagram.com, response code: 302 933 | Error accessing https://www.instagram.com, response code: 302 934 | Error accessing https://www.instagram.com, response code: 302 935 | Error accessing https://www.instagram.com, response code: 302 936 | Error accessing https://www.instagram.com, response code: 302 937 | Error accessing https://www.instagram.com, response code: 302 938 | Error accessing https://www.instagram.com, response code: 302 939 | Error accessing https://www.instagram.com, response code: 302 940 | Error accessing https://www.instagram.com, response code: 302 941 | Error accessing https://www.instagram.com, response code: 302 942 | Error accessing https://www.instagram.com, response code: 302 943 | Error accessing https://www.instagram.com, response code: 302 944 | Error accessing https://www.instagram.com, response code: 302 945 | Error accessing https://www.instagram.com, response code: 302 946 | Error accessing https://www.instagram.com, response code: 302 947 | Error accessing https://www.instagram.com, response code: 302 948 | Error accessing https://www.instagram.com, response code: 302 949 | Error accessing https://www.instagram.com, response code: 302 950 | Error accessing https://www.instagram.com, response code: 302 951 | Error accessing https://www.instagram.com, response code: 302 952 | Error accessing https://www.instagram.com, response code: 302 953 | Error accessing https://www.instagram.com, response code: 302 954 | Error accessing https://www.instagram.com, response code: 302 955 | Error accessing https://www.instagram.com, response code: 302 956 | Error accessing https://www.instagram.com, response code: 302 957 | Error accessing https://www.instagram.com, response code: 302 958 | Error accessing https://www.instagram.com, response code: 302 959 | Error accessing https://www.instagram.com, response code: 302 960 | Error accessing https://www.instagram.com, response code: 302 961 | Error accessing https://www.instagram.com, response code: 302 962 | Error accessing https://www.instagram.com, response code: 302 963 | Error accessing https://www.instagram.com, response code: 302 964 | Error accessing https://www.instagram.com, response code: 302 965 | Error accessing https://www.instagram.com, response code: 302 966 | Error accessing https://www.instagram.com, response code: 302 967 | Error accessing https://www.instagram.com, response code: 302 968 | Error accessing https://www.instagram.com, response code: 302 969 | Error accessing https://www.instagram.com, response code: 302 970 | Error accessing https://www.instagram.com, response code: 302 971 | Error accessing https://www.instagram.com, response code: 302 972 | Error accessing https://www.instagram.com, response code: 302 973 | Error accessing https://www.instagram.com, response code: 302 974 | Error accessing https://www.instagram.com, response code: 302 975 | Error accessing https://www.instagram.com, response code: 302 976 | Error accessing https://www.instagram.com, response code: 302 977 | Error accessing https://www.instagram.com, response code: 302 978 | Error accessing https://www.instagram.com, response code: 302 979 | Error accessing https://www.instagram.com, response code: 302 980 | Error accessing https://www.instagram.com, response code: 302 981 | Error accessing https://www.instagram.com, response code: 302 982 | Error accessing https://www.instagram.com, response code: 302 983 | Error accessing https://www.instagram.com, response code: 302 984 | Error accessing https://www.instagram.com, response code: 302 985 | Error accessing https://www.instagram.com, response code: 302 986 | Error accessing https://www.instagram.com, response code: 302 987 | Error accessing https://www.instagram.com, response code: 302 988 | Error accessing https://www.instagram.com, response code: 302 989 | Error accessing https://www.instagram.com, response code: 302 990 | Error accessing https://www.instagram.com, response code: 302 991 | Error accessing https://www.instagram.com, response code: 302 992 | Error accessing https://www.instagram.com, response code: 302 993 | Error accessing https://www.instagram.com, response code: 302 994 | Error accessing https://www.instagram.com, response code: 302 995 | Error accessing https://www.instagram.com, response code: 302 996 | Error accessing https://www.instagram.com, response code: 302 997 | Error accessing https://www.instagram.com, response code: 302 998 | Error accessing https://www.instagram.com, response code: 302 999 | Error accessing https://www.instagram.com, response code: 302 1000 | Error accessing https://www.instagram.com, response code: 302 1001 | Error accessing https://www.instagram.com, response code: 302 1002 | Error accessing https://www.instagram.com, response code: 302 1003 | Error accessing https://www.instagram.com, response code: 302 1004 | Error accessing https://www.instagram.com, response code: 302 1005 | Error accessing https://www.instagram.com, response code: 302 1006 | Error accessing https://www.instagram.com, response code: 302 1007 | Error accessing https://www.instagram.com, response code: 302 1008 | Error accessing https://www.instagram.com, response code: 302 1009 | Error accessing https://www.instagram.com, response code: 302 1010 | Error accessing https://www.instagram.com, response code: 302 1011 | Error accessing https://www.instagram.com, response code: 302 1012 | Error accessing https://www.instagram.com, response code: 302 1013 | Error accessing https://www.instagram.com, response code: 302 1014 | Error accessing https://www.instagram.com, response code: 302 1015 | Error accessing https://www.instagram.com, response code: 302 1016 | Error accessing https://www.instagram.com, response code: 302 1017 | Error accessing https://www.instagram.com, response code: 302 1018 | Error accessing https://www.instagram.com, response code: 302 1019 | Error accessing https://www.instagram.com, response code: 302 1020 | Error accessing https://www.instagram.com, response code: 302 1021 | Error accessing https://www.instagram.com, response code: 302 1022 | Error accessing https://www.instagram.com, response code: 302 1023 | Error accessing https://www.instagram.com, response code: 302 1024 | Error accessing https://www.instagram.com, response code: 302 1025 | Error accessing https://www.instagram.com, response code: 302 1026 | Error accessing https://www.instagram.com, response code: 302 1027 | Error accessing https://www.instagram.com, response code: 302 1028 | Error accessing https://www.instagram.com, response code: 302 1029 | Error accessing https://www.instagram.com, response code: 302 1030 | Error accessing https://www.instagram.com, response code: 302 1031 | Error accessing https://www.instagram.com, response code: 302 1032 | Error accessing https://www.instagram.com, response code: 302 1033 | Error accessing https://www.instagram.com, response code: 302 1034 | Error accessing https://www.instagram.com, response code: 302 1035 | Error accessing https://www.instagram.com, response code: 302 1036 | Error accessing https://www.instagram.com, response code: 302 1037 | Error accessing https://www.instagram.com, response code: 302 1038 | Error accessing https://www.instagram.com, response code: 302 1039 | Error accessing https://www.instagram.com, response code: 302 1040 | Error accessing https://www.instagram.com, response code: 302 1041 | Error accessing https://www.instagram.com, response code: 302 1042 | Error accessing https://www.instagram.com, response code: 302 1043 | Error accessing https://www.instagram.com, response code: 302 1044 | Error accessing https://www.instagram.com, response code: 302 1045 | Error accessing https://www.instagram.com, response code: 302 1046 | Error accessing https://www.instagram.com, response code: 302 1047 | Error accessing https://www.instagram.com, response code: 302 1048 | Error accessing https://www.instagram.com, response code: 302 1049 | Error accessing https://www.instagram.com, response code: 302 1050 | Error accessing https://www.instagram.com, response code: 302 1051 | Error accessing https://www.instagram.com, response code: 302 1052 | Error accessing https://www.instagram.com, response code: 302 1053 | Error accessing https://www.instagram.com, response code: 302 1054 | Error accessing https://www.instagram.com, response code: 302 1055 | Error accessing https://www.instagram.com, response code: 302 1056 | Error accessing https://www.instagram.com, response code: 302 1057 | Error accessing https://www.instagram.com, response code: 302 1058 | Error accessing https://www.instagram.com, response code: 302 1059 | Error accessing https://www.instagram.com, response code: 302 1060 | Error accessing https://www.instagram.com, response code: 302 1061 | Error accessing https://www.instagram.com, response code: 302 1062 | Error accessing https://www.instagram.com, response code: 302 1063 | Error accessing https://www.instagram.com, response code: 302 1064 | Error accessing https://www.instagram.com, response code: 302 1065 | Error accessing https://www.instagram.com, response code: 302 1066 | Error accessing https://www.instagram.com, response code: 302 1067 | Error accessing https://www.instagram.com, response code: 302 1068 | Error accessing https://www.instagram.com, response code: 302 1069 | Error accessing https://www.instagram.com, response code: 302 1070 | Error accessing https://www.instagram.com, response code: 302 1071 | Error accessing https://www.instagram.com, response code: 302 1072 | Error accessing https://www.instagram.com, response code: 302 1073 | Error accessing https://www.instagram.com, response code: 302 1074 | Error accessing https://www.instagram.com, response code: 302 1075 | Error accessing https://www.instagram.com, response code: 302 1076 | Error accessing https://www.instagram.com, response code: 302 1077 | Error accessing https://www.instagram.com, response code: 302 1078 | Error accessing https://www.instagram.com, response code: 302 1079 | Error accessing https://www.instagram.com, response code: 302 1080 | Error accessing https://www.instagram.com, response code: 302 1081 | Error accessing https://www.instagram.com, response code: 302 1082 | Error accessing https://www.instagram.com, response code: 302 1083 | Error accessing https://www.instagram.com, response code: 302 1084 | Error accessing https://www.instagram.com, response code: 302 1085 | Error accessing https://www.instagram.com, response code: 302 1086 | Error accessing https://www.instagram.com, response code: 302 1087 | Error accessing https://www.instagram.com, response code: 302 1088 | Error accessing https://www.instagram.com, response code: 302 1089 | Error accessing https://www.instagram.com, response code: 302 1090 | Error accessing https://www.instagram.com, response code: 302 1091 | Error accessing https://www.instagram.com, response code: 302 1092 | Error accessing https://www.instagram.com, response code: 302 1093 | Error accessing https://www.instagram.com, response code: 302 1094 | Error accessing https://www.instagram.com, response code: 302 1095 | Error accessing https://www.instagram.com, response code: 302 1096 | Error accessing https://www.instagram.com, response code: 302 1097 | Error accessing https://www.instagram.com, response code: 302 1098 | Error accessing https://www.instagram.com, response code: 302 1099 | Error accessing https://www.instagram.com, response code: 302 1100 | Error accessing https://www.instagram.com, response code: 302 1101 | Error accessing https://www.instagram.com, response code: 302 1102 | Error accessing https://www.instagram.com, response code: 302 1103 | Error accessing https://www.instagram.com, response code: 302 1104 | Error accessing https://www.instagram.com, response code: 302 1105 | Error accessing https://www.instagram.com, response code: 302 1106 | Error accessing https://www.instagram.com, response code: 302 1107 | Error accessing https://www.instagram.com, response code: 302 1108 | Error accessing https://www.instagram.com, response code: 302 1109 | Error accessing https://www.instagram.com, response code: 302 1110 | Error accessing https://www.instagram.com, response code: 302 1111 | Error accessing https://www.instagram.com, response code: 302 1112 | Error accessing https://www.instagram.com, response code: 302 1113 | Error accessing https://www.instagram.com, response code: 302 1114 | Error accessing https://www.instagram.com, response code: 302 1115 | Error accessing https://www.instagram.com, response code: 302 1116 | Error accessing https://www.instagram.com, response code: 302 1117 | Error accessing https://www.instagram.com, response code: 302 1118 | Error accessing https://www.instagram.com, response code: 302 1119 | Error accessing https://www.instagram.com, response code: 302 1120 | Error accessing https://www.instagram.com, response code: 302 1121 | Error accessing https://www.instagram.com, response code: 302 1122 | Error accessing https://www.instagram.com, response code: 302 1123 | Error accessing https://www.instagram.com, response code: 302 1124 | Error accessing https://www.instagram.com, response code: 302 1125 | Error accessing https://www.instagram.com, response code: 302 1126 | Error accessing https://www.instagram.com, response code: 302 1127 | Error accessing https://www.instagram.com, response code: 302 1128 | Error accessing https://www.instagram.com, response code: 302 1129 | Error accessing https://www.instagram.com, response code: 302 1130 | Error accessing https://www.instagram.com, response code: 302 1131 | Error accessing https://www.instagram.com, response code: 302 1132 | Error accessing https://www.instagram.com, response code: 302 1133 | Error accessing https://www.instagram.com, response code: 302 1134 | Error accessing https://www.instagram.com, response code: 302 1135 | Error accessing https://www.instagram.com, response code: 302 1136 | Error accessing https://www.instagram.com, response code: 302 1137 | Error accessing https://www.instagram.com, response code: 302 1138 | Error accessing https://www.instagram.com, response code: 302 1139 | Error accessing https://www.instagram.com, response code: 302 1140 | Error accessing https://www.instagram.com, response code: 302 1141 | Error accessing https://www.instagram.com, response code: 302 1142 | Error accessing https://www.instagram.com, response code: 302 1143 | Error accessing https://www.instagram.com, response code: 302 1144 | Error accessing https://www.instagram.com, response code: 302 1145 | Error accessing https://www.instagram.com, response code: 302 1146 | Error accessing https://www.instagram.com, response code: 302 1147 | Error accessing https://www.instagram.com, response code: 302 1148 | Error accessing https://www.instagram.com, response code: 302 1149 | Error accessing https://www.instagram.com, response code: 302 1150 | Error accessing https://www.instagram.com, response code: 302 1151 | Error accessing https://www.instagram.com, response code: 302 1152 | Error accessing https://www.instagram.com, response code: 302 1153 | Error accessing https://www.instagram.com, response code: 302 1154 | Error accessing https://www.instagram.com, response code: 302 1155 | Error accessing https://www.instagram.com, response code: 302 1156 | Error accessing https://www.instagram.com, response code: 302 1157 | Error accessing https://www.instagram.com, response code: 302 1158 | Error accessing https://www.instagram.com, response code: 302 1159 | Error accessing https://www.instagram.com, response code: 302 1160 | Error accessing https://www.instagram.com, response code: 302 1161 | Error accessing https://www.instagram.com, response code: 302 1162 | Error accessing https://www.instagram.com, response code: 302 1163 | Error accessing https://www.instagram.com, response code: 302 1164 | Error accessing https://www.instagram.com, response code: 302 1165 | Error accessing https://www.instagram.com, response code: 302 1166 | Error accessing https://www.instagram.com, response code: 302 1167 | Error accessing https://www.instagram.com, response code: 302 1168 | Error accessing https://www.instagram.com, response code: 302 1169 | Error accessing https://www.instagram.com, response code: 302 1170 | Error accessing https://www.instagram.com, response code: 302 1171 | Error accessing https://www.instagram.com, response code: 302 1172 | Error accessing https://www.instagram.com, response code: 302 1173 | Error accessing https://www.instagram.com, response code: 302 1174 | Error accessing https://www.instagram.com, response code: 302 1175 | Error accessing https://www.instagram.com, response code: 302 1176 | Error accessing https://www.instagram.com, response code: 302 1177 | Error accessing https://www.instagram.com, response code: 302 1178 | Error accessing https://www.instagram.com, response code: 302 1179 | Error accessing https://www.instagram.com, response code: 302 1180 | Error accessing https://www.instagram.com, response code: 302 1181 | Error accessing https://www.instagram.com, response code: 302 1182 | Error accessing https://www.instagram.com, response code: 302 1183 | Error accessing https://www.instagram.com, response code: 302 1184 | Error accessing https://www.instagram.com, response code: 302 1185 | Error accessing https://www.instagram.com, response code: 302 1186 | Error accessing https://www.instagram.com, response code: 302 1187 | Error accessing https://www.instagram.com, response code: 302 1188 | Error accessing https://www.instagram.com, response code: 302 1189 | Error accessing https://www.instagram.com, response code: 302 1190 | Error accessing https://www.instagram.com, response code: 302 1191 | Error accessing https://www.instagram.com, response code: 302 1192 | Error accessing https://www.instagram.com, response code: 302 1193 | Error accessing https://www.instagram.com, response code: 302 1194 | Error accessing https://www.instagram.com, response code: 302 1195 | Error accessing https://www.instagram.com, response code: 302 1196 | Error accessing https://www.instagram.com, response code: 302 1197 | Error accessing https://www.instagram.com, response code: 302 1198 | Error accessing https://www.instagram.com, response code: 302 1199 | Error accessing https://www.instagram.com, response code: 302 1200 | Error accessing https://www.instagram.com, response code: 302 1201 | Error accessing https://www.instagram.com, response code: 302 1202 | Error accessing https://www.instagram.com, response code: 302 1203 | Error accessing https://www.instagram.com, response code: 302 1204 | Error accessing https://www.instagram.com, response code: 302 1205 | Error accessing https://www.instagram.com, response code: 302 1206 | Error accessing https://www.instagram.com, response code: 302 1207 | Error accessing https://www.instagram.com, response code: 302 1208 | Error accessing https://www.instagram.com, response code: 302 1209 | Error accessing https://www.instagram.com, response code: 302 1210 | Error accessing https://www.instagram.com, response code: 302 1211 | Error accessing https://www.instagram.com, response code: 302 1212 | Error accessing https://www.instagram.com, response code: 302 1213 | Error accessing https://www.instagram.com, response code: 302 1214 | Error accessing https://www.instagram.com, response code: 302 1215 | Error accessing https://www.instagram.com, response code: 302 1216 | Error accessing https://www.instagram.com, response code: 302 1217 | Error accessing https://www.instagram.com, response code: 302 1218 | Error accessing https://www.instagram.com, response code: 302 1219 | Error accessing https://www.instagram.com, response code: 302 1220 | Error accessing https://www.instagram.com, response code: 302 1221 | Error accessing https://www.instagram.com, response code: 302 1222 | Error accessing https://www.instagram.com, response code: 302 1223 | Error accessing https://www.instagram.com, response code: 302 1224 | Error accessing https://www.instagram.com, response code: 302 1225 | Error accessing https://www.instagram.com, response code: 302 1226 | Error accessing https://www.instagram.com, response code: 302 1227 | Error accessing https://www.instagram.com, response code: 302 1228 | Error accessing https://www.instagram.com, response code: 302 1229 | Error accessing https://www.instagram.com, response code: 302 1230 | Error accessing https://www.instagram.com, response code: 302 1231 | Error accessing https://www.instagram.com, response code: 302 1232 | Error accessing https://www.instagram.com, response code: 302 1233 | Error accessing https://www.instagram.com, response code: 302 1234 | Error accessing https://www.instagram.com, response code: 302 1235 | Error accessing https://www.instagram.com, response code: 302 1236 | Error accessing https://www.instagram.com, response code: 302 1237 | Error accessing https://www.instagram.com, response code: 302 1238 | Error accessing https://www.instagram.com, response code: 302 1239 | Error accessing https://www.instagram.com, response code: 302 1240 | Error accessing https://www.instagram.com, response code: 302 1241 | Error accessing https://www.instagram.com, response code: 302 1242 | Error accessing https://www.instagram.com, response code: 302 1243 | Error accessing https://www.instagram.com, response code: 302 1244 | Error accessing https://www.instagram.com, response code: 302 1245 | Error accessing https://www.instagram.com, response code: 302 1246 | Error accessing https://www.instagram.com, response code: 302 1247 | Error accessing https://www.instagram.com, response code: 302 1248 | Error accessing https://www.instagram.com, response code: 302 1249 | Error accessing https://www.instagram.com, response code: 302 1250 | Error accessing https://www.instagram.com, response code: 302 1251 | Error accessing https://www.instagram.com, response code: 302 1252 | Error accessing https://www.instagram.com, response code: 302 1253 | Error accessing https://www.instagram.com, response code: 302 1254 | Error accessing https://www.instagram.com, response code: 302 1255 | Error accessing https://www.instagram.com, response code: 302 1256 | Error accessing https://www.instagram.com, response code: 302 1257 | Error accessing https://www.instagram.com, response code: 302 1258 | Error accessing https://www.instagram.com, response code: 302 1259 | Error accessing https://www.instagram.com, response code: 302 1260 | Error accessing https://www.instagram.com, response code: 302 1261 | Error accessing https://www.instagram.com, response code: 302 1262 | Error accessing https://www.instagram.com, response code: 302 1263 | Error accessing https://www.instagram.com, response code: 302 1264 | Error accessing https://www.instagram.com, response code: 302 1265 | Error accessing https://www.instagram.com, response code: 302 1266 | Error accessing https://www.instagram.com, response code: 302 1267 | Error accessing https://www.instagram.com, response code: 302 1268 | Error accessing https://www.instagram.com, response code: 302 1269 | Error accessing https://www.instagram.com, response code: 302 1270 | Error accessing https://www.instagram.com, response code: 302 1271 | Error accessing https://www.instagram.com, response code: 302 1272 | Error accessing https://www.instagram.com, response code: 302 1273 | Error accessing https://www.instagram.com, response code: 302 1274 | Error accessing https://www.instagram.com, response code: 302 1275 | Error accessing https://www.instagram.com, response code: 302 1276 | Error accessing https://www.instagram.com, response code: 302 1277 | Error accessing https://www.instagram.com, response code: 302 1278 | Error accessing https://www.instagram.com, response code: 302 1279 | Error accessing https://www.instagram.com, response code: 302 1280 | Error accessing https://www.instagram.com, response code: 302 1281 | Error accessing https://www.instagram.com, response code: 302 1282 | Error accessing https://www.instagram.com, response code: 302 1283 | Error accessing https://www.instagram.com, response code: 302 1284 | Error accessing https://www.instagram.com, response code: 302 1285 | Error accessing https://www.instagram.com, response code: 302 1286 | Error accessing https://www.instagram.com, response code: 302 1287 | Error accessing https://www.instagram.com, response code: 302 1288 | Error accessing https://www.instagram.com, response code: 302 1289 | Error accessing https://www.instagram.com, response code: 302 1290 | Error accessing https://www.instagram.com, response code: 302 1291 | Error accessing https://www.instagram.com, response code: 302 1292 | Error accessing https://www.instagram.com, response code: 302 1293 | Error accessing https://www.instagram.com, response code: 302 1294 | Error accessing https://www.instagram.com, response code: 302 1295 | Error accessing https://www.instagram.com, response code: 302 1296 | Error accessing https://www.instagram.com, response code: 302 1297 | Error accessing https://www.instagram.com, response code: 302 1298 | Error accessing https://www.instagram.com, response code: 302 1299 | Error accessing https://www.instagram.com, response code: 302 1300 | Error accessing https://www.instagram.com, response code: 302 1301 | Error accessing https://www.instagram.com, response code: 302 1302 | Error accessing https://www.instagram.com, response code: 302 1303 | Error accessing https://www.instagram.com, response code: 302 1304 | Error accessing https://www.instagram.com, response code: 302 1305 | Error accessing https://www.instagram.com, response code: 302 1306 | Error accessing https://www.instagram.com, response code: 302 1307 | Error accessing https://www.instagram.com, response code: 302 1308 | Error accessing https://www.instagram.com, response code: 302 1309 | Error accessing https://www.instagram.com, response code: 302 1310 | Error accessing https://www.instagram.com, response code: 302 1311 | Error accessing https://www.instagram.com, response code: 302 1312 | Error accessing https://www.instagram.com, response code: 302 1313 | Error accessing https://www.instagram.com, response code: 302 1314 | Error accessing https://www.instagram.com, response code: 302 1315 | Error accessing https://www.instagram.com, response code: 302 1316 | Error accessing https://www.instagram.com, response code: 302 1317 | Error accessing https://www.instagram.com, response code: 302 1318 | Error accessing https://www.instagram.com, response code: 302 1319 | Error accessing https://www.instagram.com, response code: 302 1320 | Error accessing https://www.instagram.com, response code: 302 1321 | Error accessing https://www.instagram.com, response code: 302 1322 | Error accessing https://www.instagram.com, response code: 302 1323 | Error accessing https://www.instagram.com, response code: 302 1324 | Error accessing https://www.instagram.com, response code: 302 1325 | Error accessing https://www.instagram.com, response code: 302 1326 | Error accessing https://www.instagram.com, response code: 302 1327 | Error accessing https://www.instagram.com, response code: 302 1328 | Error accessing https://www.instagram.com, response code: 302 1329 | Error accessing https://www.instagram.com, response code: 302 1330 | Error accessing https://www.instagram.com, response code: 302 1331 | Error accessing https://www.instagram.com, response code: 302 1332 | Error accessing https://www.instagram.com, response code: 302 1333 | Error accessing https://www.instagram.com, response code: 302 1334 | Error accessing https://www.instagram.com, response code: 302 1335 | Error accessing https://www.instagram.com, response code: 302 1336 | Error accessing https://www.instagram.com, response code: 302 1337 | Error accessing https://www.instagram.com, response code: 302 1338 | Error accessing https://www.instagram.com, response code: 302 1339 | Error accessing https://www.instagram.com, response code: 302 1340 | Error accessing https://www.instagram.com, response code: 302 1341 | Error accessing https://www.instagram.com, response code: 302 1342 | Error accessing https://www.instagram.com, response code: 302 1343 | Error accessing https://www.instagram.com, response code: 302 1344 | Error accessing https://www.instagram.com, response code: 302 1345 | Error accessing https://www.instagram.com, response code: 302 1346 | Error accessing https://www.instagram.com, response code: 302 1347 | Error accessing https://www.instagram.com, response code: 302 1348 | Error accessing https://www.instagram.com, response code: 302 1349 | Error accessing https://www.instagram.com, response code: 302 1350 | Error accessing https://www.instagram.com, response code: 302 1351 | Error accessing https://www.instagram.com, response code: 302 1352 | Error accessing https://www.instagram.com, response code: 302 1353 | Error accessing https://www.instagram.com, response code: 302 1354 | Error accessing https://www.instagram.com, response code: 302 1355 | Error accessing https://www.instagram.com, response code: 302 1356 | Error accessing https://www.instagram.com, response code: 302 1357 | Error accessing https://www.instagram.com, response code: 302 1358 | Error accessing https://www.instagram.com, response code: 302 1359 | Error accessing https://www.instagram.com, response code: 302 1360 | Error accessing https://www.instagram.com, response code: 302 1361 | Error accessing https://www.instagram.com, response code: 302 1362 | Error accessing https://www.instagram.com, response code: 302 1363 | Error accessing https://www.instagram.com, response code: 302 1364 | Error accessing https://www.instagram.com, response code: 302 1365 | Error accessing https://www.instagram.com, response code: 302 1366 | Error accessing https://www.instagram.com, response code: 302 1367 | Error accessing https://www.instagram.com, response code: 302 1368 | Error accessing https://www.instagram.com, response code: 302 1369 | Error accessing https://www.instagram.com, response code: 302 1370 | Error accessing https://www.instagram.com, response code: 302 1371 | Error accessing https://www.instagram.com, response code: 302 1372 | Error accessing https://www.instagram.com, response code: 302 1373 | Error accessing https://www.instagram.com, response code: 302 1374 | Error accessing https://www.instagram.com, response code: 302 1375 | Error accessing https://www.instagram.com, response code: 302 1376 | Error accessing https://www.instagram.com, response code: 302 1377 | Error accessing https://www.instagram.com, response code: 302 1378 | Error accessing https://www.instagram.com, response code: 302 1379 | Error accessing https://www.instagram.com, response code: 302 1380 | Error accessing https://www.instagram.com, response code: 302 1381 | Error accessing https://www.instagram.com, response code: 302 1382 | Error accessing https://www.instagram.com, response code: 302 1383 | Error accessing https://www.instagram.com, response code: 302 1384 | Error accessing https://www.instagram.com, response code: 302 1385 | Error accessing https://www.instagram.com, response code: 302 1386 | Error accessing https://www.instagram.com, response code: 302 1387 | Error accessing https://www.instagram.com, response code: 302 1388 | Error accessing https://www.instagram.com, response code: 302 1389 | Error accessing https://www.instagram.com, response code: 302 1390 | Error accessing https://www.instagram.com, response code: 302 1391 | Error accessing https://www.instagram.com, response code: 302 1392 | Error accessing https://www.instagram.com, response code: 302 1393 | Error accessing https://www.instagram.com, response code: 302 1394 | Error accessing https://www.instagram.com, response code: 302 1395 | Error accessing https://www.instagram.com, response code: 302 1396 | Error accessing https://www.instagram.com, response code: 302 1397 | Error accessing https://www.instagram.com, response code: 302 1398 | Error accessing https://www.instagram.com, response code: 302 1399 | Error accessing https://www.instagram.com, response code: 302 1400 | Error accessing https://www.instagram.com, response code: 302 1401 | Error accessing https://www.instagram.com, response code: 302 1402 | Error accessing https://www.instagram.com, response code: 302 1403 | Error accessing https://www.instagram.com, response code: 302 1404 | Error accessing https://www.instagram.com, response code: 302 1405 | Error accessing https://www.instagram.com, response code: 302 1406 | Error accessing https://www.instagram.com, response code: 302 1407 | Error accessing https://www.instagram.com, response code: 302 1408 | Error accessing https://www.instagram.com, response code: 302 1409 | Error accessing https://www.instagram.com, response code: 302 1410 | Error accessing https://www.instagram.com, response code: 302 1411 | Error accessing https://www.instagram.com, response code: 302 1412 | Error accessing https://www.instagram.com, response code: 302 1413 | Error accessing https://www.instagram.com, response code: 302 1414 | Error accessing https://www.instagram.com, response code: 302 1415 | Error accessing https://www.instagram.com, response code: 302 1416 | Error accessing https://www.instagram.com, response code: 302 1417 | Error accessing https://www.instagram.com, response code: 302 1418 | Error accessing https://www.instagram.com, response code: 302 1419 | Error accessing https://www.instagram.com, response code: 302 1420 | Error accessing https://www.instagram.com, response code: 302 1421 | Error accessing https://www.instagram.com, response code: 302 1422 | Error accessing https://www.instagram.com, response code: 302 1423 | Error accessing https://www.instagram.com, response code: 302 1424 | Error accessing https://www.instagram.com, response code: 302 1425 | Error accessing https://www.instagram.com, response code: 302 1426 | Error accessing https://www.instagram.com, response code: 302 1427 | Error accessing https://www.instagram.com, response code: 302 1428 | Error accessing https://www.instagram.com, response code: 302 1429 | Error accessing https://www.instagram.com, response code: 302 1430 | Error accessing https://www.instagram.com, response code: 302 1431 | Error accessing https://www.instagram.com, response code: 302 1432 | Error accessing https://www.instagram.com, response code: 302 1433 | Error accessing https://www.instagram.com, response code: 302 1434 | Error accessing https://www.instagram.com, response code: 302 1435 | -------------------------------------------------------------------------------- /logs/linkedin_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.amazon.com, response code: 2 | Error accessing https://www.amazon.com, response code: 3 | Error accessing https://www.amazon.com, response code: 4 | Error accessing https://www.amazon.com, response code: 5 | Error accessing https://www.linkedin.com, response code: 6 | Error accessing https://www.linkedin.com, response code: 7 | Error accessing https://www.linkedin.com, response code: 8 | Error accessing https://www.linkedin.com, response code: 9 | Error accessing https://www.linkedin.com, response code: 10 | Error accessing https://www.linkedin.com, response code: 11 | Error accessing https://www.linkedin.com, response code: 12 | Error accessing https://www.linkedin.com, response code: 13 | Error accessing https://www.linkedin.com, response code: 14 | Error accessing https://www.linkedin.com, response code: 15 | Error accessing https://www.linkedin.com, response code: 16 | Error accessing https://www.linkedin.com, response code: 17 | Error accessing https://www.linkedin.com, response code: 18 | Error accessing https://www.linkedin.com, response code: 19 | Error accessing https://www.linkedin.com, response code: 20 | Error accessing https://www.linkedin.com, response code: 21 | Error accessing https://www.linkedin.com, response code: 22 | Error accessing https://www.linkedin.com, response code: 23 | Error accessing https://www.linkedin.com, response code: 24 | Error accessing https://www.linkedin.com, response code: 25 | Error accessing https://www.linkedin.com, response code: 26 | Error accessing https://www.linkedin.com, response code: 27 | Error accessing https://www.linkedin.com, response code: 28 | Error accessing https://www.linkedin.com, response code: 29 | Error accessing https://www.linkedin.com, response code: 30 | Error accessing https://www.linkedin.com, response code: 31 | Error accessing https://www.linkedin.com, response code: 32 | Error accessing https://www.linkedin.com, response code: 33 | Error accessing https://www.linkedin.com, response code: 34 | Error accessing https://www.linkedin.com, response code: 35 | Error accessing https://www.linkedin.com, response code: 36 | Error accessing https://www.linkedin.com, response code: 37 | Error accessing https://www.linkedin.com, response code: 38 | Error accessing https://www.linkedin.com, response code: 39 | Error accessing https://www.linkedin.com, response code: 40 | Error accessing https://www.linkedin.com, response code: 41 | Error accessing https://www.linkedin.com, response code: 42 | Error accessing https://www.linkedin.com, response code: 43 | Error accessing https://www.linkedin.com, response code: 44 | Error accessing https://www.linkedin.com, response code: 45 | Error accessing https://www.linkedin.com, response code: 46 | Error accessing https://www.linkedin.com, response code: 47 | Error accessing https://www.linkedin.com, response code: 48 | Error accessing https://www.linkedin.com, response code: 49 | Error accessing https://www.linkedin.com, response code: 50 | Error accessing https://www.linkedin.com, response code: 51 | Error accessing https://www.linkedin.com, response code: 52 | Error accessing https://www.linkedin.com, response code: 53 | Error accessing https://www.linkedin.com, response code: 54 | Error accessing https://www.linkedin.com, response code: 55 | Error accessing https://www.linkedin.com, response code: 56 | Error accessing https://www.linkedin.com, response code: 57 | Error accessing https://www.linkedin.com, response code: 58 | Error accessing https://www.linkedin.com, response code: 59 | Error accessing https://www.linkedin.com, response code: 60 | Error accessing https://www.linkedin.com, response code: 61 | Error accessing https://www.linkedin.com, response code: 62 | Error accessing https://www.linkedin.com, response code: 63 | Error accessing https://www.linkedin.com, response code: 64 | Error accessing https://www.linkedin.com, response code: 65 | Error accessing https://www.linkedin.com, response code: 66 | Error accessing https://www.linkedin.com, response code: 67 | Error accessing https://www.linkedin.com, response code: 68 | Error accessing https://www.linkedin.com, response code: 69 | Error accessing https://www.linkedin.com, response code: 70 | Error accessing https://www.linkedin.com, response code: 71 | Error accessing https://www.linkedin.com, response code: 72 | Error accessing https://www.linkedin.com, response code: 73 | Error accessing https://www.linkedin.com, response code: 74 | Error accessing https://www.linkedin.com, response code: 75 | Error accessing https://www.linkedin.com, response code: 76 | Error accessing https://www.linkedin.com, response code: 77 | Error accessing https://www.linkedin.com, response code: 78 | Error accessing https://www.linkedin.com, response code: 79 | Error accessing https://www.linkedin.com, response code: 80 | Error accessing https://www.linkedin.com, response code: 81 | Error accessing https://www.linkedin.com, response code: 82 | Error accessing https://www.linkedin.com, response code: 83 | Error accessing https://www.linkedin.com, response code: 84 | Error accessing https://www.linkedin.com, response code: 85 | Error accessing https://www.linkedin.com, response code: 86 | Error accessing https://www.linkedin.com, response code: 87 | Error accessing https://www.linkedin.com, response code: 88 | Error accessing https://www.linkedin.com, response code: 89 | Error accessing https://www.linkedin.com, response code: 90 | Error accessing https://www.linkedin.com, response code: 91 | Error accessing https://www.linkedin.com, response code: 92 | Error accessing https://www.linkedin.com, response code: 93 | Error accessing https://www.linkedin.com, response code: 94 | Error accessing https://www.linkedin.com, response code: 95 | Error accessing https://www.linkedin.com, response code: 96 | Error accessing https://www.linkedin.com, response code: 97 | Error accessing https://www.linkedin.com, response code: 98 | Error accessing https://www.linkedin.com, response code: 99 | Error accessing https://www.linkedin.com, response code: 100 | Error accessing https://www.linkedin.com, response code: 101 | Error accessing https://www.linkedin.com, response code: 102 | Error accessing https://www.linkedin.com, response code: 103 | Error accessing https://www.linkedin.com, response code: 104 | Error accessing https://www.linkedin.com, response code: 105 | Error accessing https://www.linkedin.com, response code: 106 | Error accessing https://www.linkedin.com, response code: 107 | Error accessing https://www.linkedin.com, response code: 108 | Error accessing https://www.linkedin.com, response code: 109 | Error accessing https://www.linkedin.com, response code: 110 | Error accessing https://www.linkedin.com, response code: 111 | Error accessing https://www.linkedin.com, response code: 112 | Error accessing https://www.linkedin.com, response code: 113 | Error accessing https://www.linkedin.com, response code: 114 | Error accessing https://www.linkedin.com, response code: 115 | Error accessing https://www.linkedin.com, response code: 116 | Error accessing https://www.linkedin.com, response code: 117 | Error accessing https://www.linkedin.com, response code: 118 | Error accessing https://www.linkedin.com, response code: 119 | Error accessing https://www.linkedin.com, response code: 120 | Error accessing https://www.linkedin.com, response code: 121 | Error accessing https://www.linkedin.com, response code: 122 | Error accessing https://www.linkedin.com, response code: 123 | Error accessing https://www.linkedin.com, response code: 124 | Error accessing https://www.linkedin.com, response code: 125 | Error accessing https://www.linkedin.com, response code: 126 | Error accessing https://www.linkedin.com, response code: 127 | Error accessing https://www.linkedin.com, response code: 128 | Error accessing https://www.linkedin.com, response code: 129 | Error accessing https://www.linkedin.com, response code: 130 | Error accessing https://www.linkedin.com, response code: 131 | Error accessing https://www.linkedin.com, response code: 132 | Error accessing https://www.linkedin.com, response code: 133 | Error accessing https://www.linkedin.com, response code: 134 | Error accessing https://www.linkedin.com, response code: 135 | Error accessing https://www.linkedin.com, response code: 136 | Error accessing https://www.linkedin.com, response code: 137 | Error accessing https://www.linkedin.com, response code: 138 | Error accessing https://www.linkedin.com, response code: 139 | Error accessing https://www.linkedin.com, response code: 140 | Error accessing https://www.linkedin.com, response code: 141 | Error accessing https://www.linkedin.com, response code: 142 | Error accessing https://www.linkedin.com, response code: 143 | Error accessing https://www.linkedin.com, response code: 144 | Error accessing https://www.linkedin.com, response code: 145 | Error accessing https://www.linkedin.com, response code: 146 | Error accessing https://www.linkedin.com, response code: 147 | Error accessing https://www.linkedin.com, response code: 148 | Error accessing https://www.linkedin.com, response code: 149 | Error accessing https://www.linkedin.com, response code: 150 | Error accessing https://www.linkedin.com, response code: 151 | Error accessing https://www.linkedin.com, response code: 152 | Error accessing https://www.linkedin.com, response code: 153 | Error accessing https://www.linkedin.com, response code: 154 | Error accessing https://www.linkedin.com, response code: 155 | Error accessing https://www.linkedin.com, response code: 156 | Error accessing https://www.linkedin.com, response code: 157 | Error accessing https://www.linkedin.com, response code: 158 | Error accessing https://www.linkedin.com, response code: 159 | Error accessing https://www.linkedin.com, response code: 160 | Error accessing https://www.linkedin.com, response code: 161 | Error accessing https://www.linkedin.com, response code: 162 | Error accessing https://www.linkedin.com, response code: 163 | Error accessing https://www.linkedin.com, response code: 164 | Error accessing https://www.linkedin.com, response code: 165 | Error accessing https://www.linkedin.com, response code: 166 | Error accessing https://www.linkedin.com, response code: 167 | Error accessing https://www.linkedin.com, response code: 168 | Error accessing https://www.linkedin.com, response code: 169 | Error accessing https://www.linkedin.com, response code: 170 | Error accessing https://www.linkedin.com, response code: 171 | Error accessing https://www.linkedin.com, response code: 172 | Error accessing https://www.linkedin.com, response code: 173 | Error accessing https://www.linkedin.com, response code: 174 | Error accessing https://www.linkedin.com, response code: 175 | Error accessing https://www.linkedin.com, response code: 176 | Error accessing https://www.linkedin.com, response code: 177 | Error accessing https://www.linkedin.com, response code: 178 | Error accessing https://www.linkedin.com, response code: 179 | Error accessing https://www.linkedin.com, response code: 180 | Error accessing https://www.linkedin.com, response code: 181 | Error accessing https://www.linkedin.com, response code: 182 | Error accessing https://www.linkedin.com, response code: 183 | Error accessing https://www.linkedin.com, response code: 184 | Error accessing https://www.linkedin.com, response code: 185 | Error accessing https://www.linkedin.com, response code: 186 | Error accessing https://www.linkedin.com, response code: 187 | Error accessing https://www.linkedin.com, response code: 188 | Error accessing https://www.linkedin.com, response code: 189 | Error accessing https://www.linkedin.com, response code: 190 | Error accessing https://www.linkedin.com, response code: 191 | Error accessing https://www.linkedin.com, response code: 192 | Error accessing https://www.linkedin.com, response code: 193 | Error accessing https://www.linkedin.com, response code: 194 | Error accessing https://www.linkedin.com, response code: 195 | Error accessing https://www.linkedin.com, response code: 196 | Error accessing https://www.linkedin.com, response code: 197 | Error accessing https://www.linkedin.com, response code: 198 | Error accessing https://www.linkedin.com, response code: 199 | Error accessing https://www.linkedin.com, response code: 200 | Error accessing https://www.linkedin.com, response code: 201 | Error accessing https://www.linkedin.com, response code: 202 | Error accessing https://www.linkedin.com, response code: 203 | Error accessing https://www.linkedin.com, response code: 204 | Error accessing https://www.linkedin.com, response code: 205 | Error accessing https://www.linkedin.com, response code: 206 | Error accessing https://www.linkedin.com, response code: 207 | Error accessing https://www.linkedin.com, response code: 208 | Error accessing https://www.linkedin.com, response code: 209 | Error accessing https://www.linkedin.com, response code: 210 | Error accessing https://www.linkedin.com, response code: 211 | Error accessing https://www.linkedin.com, response code: 212 | Error accessing https://www.linkedin.com, response code: 213 | Error accessing https://www.linkedin.com, response code: 214 | Error accessing https://www.linkedin.com, response code: 215 | Error accessing https://www.linkedin.com, response code: 216 | Error accessing https://www.linkedin.com, response code: 217 | Error accessing https://www.linkedin.com, response code: 218 | Error accessing https://www.linkedin.com, response code: 219 | Error accessing https://www.linkedin.com, response code: 220 | Error accessing https://www.linkedin.com, response code: 221 | Error accessing https://www.linkedin.com, response code: 222 | Error accessing https://www.linkedin.com, response code: 223 | Error accessing https://www.linkedin.com, response code: 224 | Error accessing https://www.linkedin.com, response code: 225 | Error accessing https://www.linkedin.com, response code: 226 | Error accessing https://www.linkedin.com, response code: 227 | Error accessing https://www.linkedin.com, response code: 228 | Error accessing https://www.linkedin.com, response code: 229 | Error accessing https://www.linkedin.com, response code: 230 | Error accessing https://www.linkedin.com, response code: 231 | Error accessing https://www.linkedin.com, response code: 232 | Error accessing https://www.linkedin.com, response code: 233 | Error accessing https://www.linkedin.com, response code: 234 | Error accessing https://www.linkedin.com, response code: 235 | Error accessing https://www.linkedin.com, response code: 236 | Error accessing https://www.linkedin.com, response code: 237 | Error accessing https://www.linkedin.com, response code: 238 | Error accessing https://www.linkedin.com, response code: 239 | Error accessing https://www.linkedin.com, response code: 240 | Error accessing https://www.linkedin.com, response code: 241 | Error accessing https://www.linkedin.com, response code: 242 | Error accessing https://www.linkedin.com, response code: 243 | Error accessing https://www.linkedin.com, response code: 244 | Error accessing https://www.linkedin.com, response code: 245 | Error accessing https://www.linkedin.com, response code: 246 | Error accessing https://www.linkedin.com, response code: 247 | Error accessing https://www.linkedin.com, response code: 248 | Error accessing https://www.linkedin.com, response code: 249 | Error accessing https://www.linkedin.com, response code: 250 | Error accessing https://www.linkedin.com, response code: 251 | Error accessing https://www.linkedin.com, response code: 252 | Error accessing https://www.linkedin.com, response code: 253 | Error accessing https://www.linkedin.com, response code: 254 | Error accessing https://www.linkedin.com, response code: 255 | Error accessing https://www.linkedin.com, response code: 256 | Error accessing https://www.linkedin.com, response code: 257 | Error accessing https://www.linkedin.com, response code: 258 | Error accessing https://www.linkedin.com, response code: 259 | Error accessing https://www.linkedin.com, response code: 260 | Error accessing https://www.linkedin.com, response code: 261 | Error accessing https://www.linkedin.com, response code: 262 | Error accessing https://www.linkedin.com, response code: 263 | Error accessing https://www.linkedin.com, response code: 264 | Error accessing https://www.linkedin.com, response code: 265 | Error accessing https://www.linkedin.com, response code: 266 | Error accessing https://www.linkedin.com, response code: 267 | Error accessing https://www.linkedin.com, response code: 268 | Error accessing https://www.linkedin.com, response code: 269 | Error accessing https://www.linkedin.com, response code: 270 | Error accessing https://www.linkedin.com, response code: 271 | Error accessing https://www.linkedin.com, response code: 272 | Error accessing https://www.linkedin.com, response code: 273 | Error accessing https://www.linkedin.com, response code: 274 | Error accessing https://www.linkedin.com, response code: 275 | Error accessing https://www.linkedin.com, response code: 276 | Error accessing https://www.linkedin.com, response code: 277 | Error accessing https://www.linkedin.com, response code: 278 | Error accessing https://www.linkedin.com, response code: 279 | Error accessing https://www.linkedin.com, response code: 280 | Error accessing https://www.linkedin.com, response code: 281 | Error accessing https://www.linkedin.com, response code: 282 | Error accessing https://www.linkedin.com, response code: 283 | Error accessing https://www.linkedin.com, response code: 284 | Error accessing https://www.linkedin.com, response code: 285 | Error accessing https://www.linkedin.com, response code: 286 | Error accessing https://www.linkedin.com, response code: 287 | Error accessing https://www.linkedin.com, response code: 288 | Error accessing https://www.linkedin.com, response code: 289 | Error accessing https://www.linkedin.com, response code: 290 | Error accessing https://www.linkedin.com, response code: 291 | Error accessing https://www.linkedin.com, response code: 292 | Error accessing https://www.linkedin.com, response code: 293 | Error accessing https://www.linkedin.com, response code: 294 | Error accessing https://www.linkedin.com, response code: 295 | Error accessing https://www.linkedin.com, response code: 296 | Error accessing https://www.linkedin.com, response code: 297 | Error accessing https://www.linkedin.com, response code: 298 | Error accessing https://www.linkedin.com, response code: 299 | Error accessing https://www.linkedin.com, response code: 300 | Error accessing https://www.linkedin.com, response code: 301 | Error accessing https://www.linkedin.com, response code: 302 | Error accessing https://www.linkedin.com, response code: 303 | Error accessing https://www.linkedin.com, response code: 304 | Error accessing https://www.linkedin.com, response code: 305 | Error accessing https://www.linkedin.com, response code: 306 | Error accessing https://www.linkedin.com, response code: 307 | Error accessing https://www.linkedin.com, response code: 308 | Error accessing https://www.linkedin.com, response code: 309 | Error accessing https://www.linkedin.com, response code: 310 | Error accessing https://www.linkedin.com, response code: 311 | Error accessing https://www.linkedin.com, response code: 312 | Error accessing https://www.linkedin.com, response code: 313 | Error accessing https://www.linkedin.com, response code: 314 | Error accessing https://www.linkedin.com, response code: 315 | Error accessing https://www.linkedin.com, response code: 316 | Error accessing https://www.linkedin.com, response code: 317 | Error accessing https://www.linkedin.com, response code: 318 | Error accessing https://www.linkedin.com, response code: 319 | Error accessing https://www.linkedin.com, response code: 320 | Error accessing https://www.linkedin.com, response code: 321 | Error accessing https://www.linkedin.com, response code: 322 | Error accessing https://www.linkedin.com, response code: 323 | Error accessing https://www.linkedin.com, response code: 324 | Error accessing https://www.linkedin.com, response code: 325 | Error accessing https://www.linkedin.com, response code: 326 | Error accessing https://www.linkedin.com, response code: 327 | Error accessing https://www.linkedin.com, response code: 328 | Error accessing https://www.linkedin.com, response code: 329 | Error accessing https://www.linkedin.com, response code: 330 | Error accessing https://www.linkedin.com, response code: 331 | Error accessing https://www.linkedin.com, response code: 332 | Error accessing https://www.linkedin.com, response code: 333 | Error accessing https://www.linkedin.com, response code: 334 | Error accessing https://www.linkedin.com, response code: 335 | Error accessing https://www.linkedin.com, response code: 336 | Error accessing https://www.linkedin.com, response code: 337 | Error accessing https://www.linkedin.com, response code: 338 | Error accessing https://www.linkedin.com, response code: 339 | Error accessing https://www.linkedin.com, response code: 340 | Error accessing https://www.linkedin.com, response code: 341 | Error accessing https://www.linkedin.com, response code: 342 | Error accessing https://www.linkedin.com, response code: 343 | Error accessing https://www.linkedin.com, response code: 344 | Error accessing https://www.linkedin.com, response code: 345 | Error accessing https://www.linkedin.com, response code: 346 | Error accessing https://www.linkedin.com, response code: 347 | Error accessing https://www.linkedin.com, response code: 348 | Error accessing https://www.linkedin.com, response code: 349 | Error accessing https://www.linkedin.com, response code: 350 | Error accessing https://www.linkedin.com, response code: 351 | Error accessing https://www.linkedin.com, response code: 352 | Error accessing https://www.linkedin.com, response code: 353 | Error accessing https://www.linkedin.com, response code: 354 | Error accessing https://www.linkedin.com, response code: 355 | Error accessing https://www.linkedin.com, response code: 356 | Error accessing https://www.linkedin.com, response code: 357 | Error accessing https://www.linkedin.com, response code: 358 | Error accessing https://www.linkedin.com, response code: 359 | Error accessing https://www.linkedin.com, response code: 360 | Error accessing https://www.linkedin.com, response code: 361 | Error accessing https://www.linkedin.com, response code: 362 | Error accessing https://www.linkedin.com, response code: 363 | Error accessing https://www.linkedin.com, response code: 364 | Error accessing https://www.linkedin.com, response code: 365 | Error accessing https://www.linkedin.com, response code: 366 | Error accessing https://www.linkedin.com, response code: 367 | Error accessing https://www.linkedin.com, response code: 368 | Error accessing https://www.linkedin.com, response code: 369 | Error accessing https://www.linkedin.com, response code: 370 | Error accessing https://www.linkedin.com, response code: 371 | Error accessing https://www.linkedin.com, response code: 372 | Error accessing https://www.linkedin.com, response code: 373 | Error accessing https://www.linkedin.com, response code: 374 | Error accessing https://www.linkedin.com, response code: 375 | Error accessing https://www.linkedin.com, response code: 376 | Error accessing https://www.linkedin.com, response code: 377 | Error accessing https://www.linkedin.com, response code: 378 | Error accessing https://www.linkedin.com, response code: 379 | Error accessing https://www.linkedin.com, response code: 380 | Error accessing https://www.linkedin.com, response code: 381 | Error accessing https://www.linkedin.com, response code: 382 | Error accessing https://www.linkedin.com, response code: 383 | Error accessing https://www.linkedin.com, response code: 384 | Error accessing https://www.linkedin.com, response code: 385 | Error accessing https://www.linkedin.com, response code: 386 | Error accessing https://www.linkedin.com, response code: 387 | Error accessing https://www.linkedin.com, response code: 388 | Error accessing https://www.linkedin.com, response code: 389 | Error accessing https://www.linkedin.com, response code: 390 | Error accessing https://www.linkedin.com, response code: 391 | Error accessing https://www.linkedin.com, response code: 392 | Error accessing https://www.linkedin.com, response code: 393 | Error accessing https://www.linkedin.com, response code: 394 | Error accessing https://www.linkedin.com, response code: 395 | Error accessing https://www.linkedin.com, response code: 396 | Error accessing https://www.linkedin.com, response code: 397 | Error accessing https://www.linkedin.com, response code: 398 | Error accessing https://www.linkedin.com, response code: 399 | Error accessing https://www.linkedin.com, response code: 400 | Error accessing https://www.linkedin.com, response code: 401 | Error accessing https://www.linkedin.com, response code: 402 | Error accessing https://www.linkedin.com, response code: 403 | Error accessing https://www.linkedin.com, response code: 404 | Error accessing https://www.linkedin.com, response code: 405 | Error accessing https://www.linkedin.com, response code: 406 | Error accessing https://www.linkedin.com, response code: 407 | Error accessing https://www.linkedin.com, response code: 408 | Error accessing https://www.linkedin.com, response code: 409 | Error accessing https://www.linkedin.com, response code: 410 | Error accessing https://www.linkedin.com, response code: 411 | Error accessing https://www.linkedin.com, response code: 412 | Error accessing https://www.linkedin.com, response code: 413 | Error accessing https://www.linkedin.com, response code: 414 | Error accessing https://www.linkedin.com, response code: 415 | Error accessing https://www.linkedin.com, response code: 416 | Error accessing https://www.linkedin.com, response code: 417 | Error accessing https://www.linkedin.com, response code: 418 | Error accessing https://www.linkedin.com, response code: 419 | Error accessing https://www.linkedin.com, response code: 420 | Error accessing https://www.linkedin.com, response code: 421 | Error accessing https://www.linkedin.com, response code: 422 | Error accessing https://www.linkedin.com, response code: 423 | Error accessing https://www.linkedin.com, response code: 424 | Error accessing https://www.linkedin.com, response code: 425 | Error accessing https://www.linkedin.com, response code: 426 | Error accessing https://www.linkedin.com, response code: 427 | Error accessing https://www.linkedin.com, response code: 428 | Error accessing https://www.linkedin.com, response code: 429 | Error accessing https://www.linkedin.com, response code: 430 | Error accessing https://www.linkedin.com, response code: 431 | Error accessing https://www.linkedin.com, response code: 432 | Error accessing https://www.linkedin.com, response code: 433 | Error accessing https://www.linkedin.com, response code: 434 | Error accessing https://www.linkedin.com, response code: 435 | Error accessing https://www.linkedin.com, response code: 436 | Error accessing https://www.linkedin.com, response code: 437 | Error accessing https://www.linkedin.com, response code: 438 | Error accessing https://www.linkedin.com, response code: 439 | Error accessing https://www.linkedin.com, response code: 440 | Error accessing https://www.linkedin.com, response code: 441 | Error accessing https://www.linkedin.com, response code: 442 | Error accessing https://www.linkedin.com, response code: 443 | Error accessing https://www.linkedin.com, response code: 444 | Error accessing https://www.linkedin.com, response code: 445 | Error accessing https://www.linkedin.com, response code: 446 | Error accessing https://www.linkedin.com, response code: 447 | Error accessing https://www.linkedin.com, response code: 448 | Error accessing https://www.linkedin.com, response code: 449 | Error accessing https://www.linkedin.com, response code: 450 | Error accessing https://www.linkedin.com, response code: 451 | Error accessing https://www.linkedin.com, response code: 452 | Error accessing https://www.linkedin.com, response code: 453 | Error accessing https://www.linkedin.com, response code: 454 | Error accessing https://www.linkedin.com, response code: 455 | Error accessing https://www.linkedin.com, response code: 456 | Error accessing https://www.linkedin.com, response code: 457 | Error accessing https://www.linkedin.com, response code: 458 | Error accessing https://www.linkedin.com, response code: 459 | Error accessing https://www.linkedin.com, response code: 460 | Error accessing https://www.linkedin.com, response code: 461 | Error accessing https://www.linkedin.com, response code: 462 | Error accessing https://www.linkedin.com, response code: 463 | Error accessing https://www.linkedin.com, response code: 464 | Error accessing https://www.linkedin.com, response code: 465 | Error accessing https://www.linkedin.com, response code: 466 | Error accessing https://www.linkedin.com, response code: 467 | Error accessing https://www.linkedin.com, response code: 468 | Error accessing https://www.linkedin.com, response code: 469 | Error accessing https://www.linkedin.com, response code: 470 | Error accessing https://www.linkedin.com, response code: 471 | Error accessing https://www.linkedin.com, response code: 472 | Error accessing https://www.linkedin.com, response code: 473 | Error accessing https://www.linkedin.com, response code: 474 | Error accessing https://www.linkedin.com, response code: 475 | Error accessing https://www.linkedin.com, response code: 476 | Error accessing https://www.linkedin.com, response code: 477 | Error accessing https://www.linkedin.com, response code: 478 | Error accessing https://www.linkedin.com, response code: 479 | Error accessing https://www.linkedin.com, response code: 480 | Error accessing https://www.linkedin.com, response code: 481 | Error accessing https://www.linkedin.com, response code: 482 | Error accessing https://www.linkedin.com, response code: 483 | Error accessing https://www.linkedin.com, response code: 484 | Error accessing https://www.linkedin.com, response code: 485 | Error accessing https://www.linkedin.com, response code: 486 | Error accessing https://www.linkedin.com, response code: 487 | Error accessing https://www.linkedin.com, response code: 488 | Error accessing https://www.linkedin.com, response code: 489 | Error accessing https://www.linkedin.com, response code: 490 | Error accessing https://www.linkedin.com, response code: 491 | Error accessing https://www.linkedin.com, response code: 492 | Error accessing https://www.linkedin.com, response code: 493 | Error accessing https://www.linkedin.com, response code: 494 | Error accessing https://www.linkedin.com, response code: 495 | Error accessing https://www.linkedin.com, response code: 496 | Error accessing https://www.linkedin.com, response code: 497 | Error accessing https://www.linkedin.com, response code: 498 | Error accessing https://www.linkedin.com, response code: 499 | Error accessing https://www.linkedin.com, response code: 500 | Error accessing https://www.linkedin.com, response code: 501 | Error accessing https://www.linkedin.com, response code: 502 | Error accessing https://www.linkedin.com, response code: 503 | Error accessing https://www.linkedin.com, response code: 504 | Error accessing https://www.linkedin.com, response code: 505 | Error accessing https://www.linkedin.com, response code: 506 | Error accessing https://www.linkedin.com, response code: 507 | Error accessing https://www.linkedin.com, response code: 508 | Error accessing https://www.linkedin.com, response code: 509 | Error accessing https://www.linkedin.com, response code: 510 | Error accessing https://www.linkedin.com, response code: 511 | Error accessing https://www.linkedin.com, response code: 512 | Error accessing https://www.linkedin.com, response code: 513 | Error accessing https://www.linkedin.com, response code: 514 | Error accessing https://www.linkedin.com, response code: 515 | Error accessing https://www.linkedin.com, response code: 516 | Error accessing https://www.linkedin.com, response code: 517 | Error accessing https://www.linkedin.com, response code: 518 | Error accessing https://www.linkedin.com, response code: 519 | Error accessing https://www.linkedin.com, response code: 520 | Error accessing https://www.linkedin.com, response code: 521 | Error accessing https://www.linkedin.com, response code: 522 | Error accessing https://www.linkedin.com, response code: 523 | Error accessing https://www.linkedin.com, response code: 524 | Error accessing https://www.linkedin.com, response code: 525 | Error accessing https://www.linkedin.com, response code: 526 | Error accessing https://www.linkedin.com, response code: 527 | Error accessing https://www.linkedin.com, response code: 528 | Error accessing https://www.linkedin.com, response code: 529 | Error accessing https://www.linkedin.com, response code: 530 | Error accessing https://www.linkedin.com, response code: 531 | Error accessing https://www.linkedin.com, response code: 532 | Error accessing https://www.linkedin.com, response code: 533 | Error accessing https://www.linkedin.com, response code: 534 | Error accessing https://www.linkedin.com, response code: 535 | Error accessing https://www.linkedin.com, response code: 536 | Error accessing https://www.linkedin.com, response code: 537 | Error accessing https://www.linkedin.com, response code: 538 | Error accessing https://www.linkedin.com, response code: 539 | Error accessing https://www.linkedin.com, response code: 540 | Error accessing https://www.linkedin.com, response code: 541 | Error accessing https://www.linkedin.com, response code: 542 | Error accessing https://www.linkedin.com, response code: 543 | Error accessing https://www.linkedin.com, response code: 544 | Error accessing https://www.linkedin.com, response code: 545 | Error accessing https://www.linkedin.com, response code: 546 | Error accessing https://www.linkedin.com, response code: 547 | Error accessing https://www.linkedin.com, response code: 548 | Error accessing https://www.linkedin.com, response code: 549 | Error accessing https://www.linkedin.com, response code: 550 | Error accessing https://www.linkedin.com, response code: 551 | Error accessing https://www.linkedin.com, response code: 552 | Error accessing https://www.linkedin.com, response code: 553 | Error accessing https://www.linkedin.com, response code: 554 | Error accessing https://www.linkedin.com, response code: 555 | Error accessing https://www.linkedin.com, response code: 556 | Error accessing https://www.linkedin.com, response code: 557 | Error accessing https://www.linkedin.com, response code: 558 | Error accessing https://www.linkedin.com, response code: 559 | Error accessing https://www.linkedin.com, response code: 560 | Error accessing https://www.linkedin.com, response code: 561 | Error accessing https://www.linkedin.com, response code: 562 | Error accessing https://www.linkedin.com, response code: 563 | Error accessing https://www.linkedin.com, response code: 564 | Error accessing https://www.linkedin.com, response code: 565 | Error accessing https://www.linkedin.com, response code: 566 | Error accessing https://www.linkedin.com, response code: 567 | Error accessing https://www.linkedin.com, response code: 568 | Error accessing https://www.linkedin.com, response code: 569 | Error accessing https://www.linkedin.com, response code: 570 | Error accessing https://www.linkedin.com, response code: 571 | Error accessing https://www.linkedin.com, response code: 572 | Error accessing https://www.linkedin.com, response code: 573 | Error accessing https://www.linkedin.com, response code: 574 | Error accessing https://www.linkedin.com, response code: 575 | Error accessing https://www.linkedin.com, response code: 576 | Error accessing https://www.linkedin.com, response code: 577 | Error accessing https://www.linkedin.com, response code: 578 | Error accessing https://www.linkedin.com, response code: 579 | Error accessing https://www.linkedin.com, response code: 580 | -------------------------------------------------------------------------------- /logs/netflix_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing , response code: 000 2 | Error accessing , response code: 000 3 | Error accessing , response code: 000 4 | Error accessing , response code: 000 5 | Error accessing https://www.netflix.com, response code: 000 6 | Error accessing https://www.netflix.com, response code: 000 7 | Error accessing https://www.netflix.com, response code: 000 8 | Error accessing https://www.netflix.com, response code: 9 | Error accessing https://www.netflix.com, response code: 10 | Error accessing https://www.netflix.com, response code: 302 11 | Error accessing https://www.netflix.com, response code: 302 12 | Error accessing https://www.netflix.com, response code: 302 13 | Error accessing https://www.netflix.com, response code: 302 14 | Error accessing https://www.netflix.com, response code: 302 15 | Error accessing https://www.netflix.com, response code: 302 16 | Error accessing https://www.netflix.com, response code: 302 17 | Error accessing https://www.netflix.com, response code: 302 18 | Error accessing https://www.netflix.com, response code: 302 19 | Error accessing https://www.netflix.com, response code: 302 20 | Error accessing https://www.netflix.com, response code: 302 21 | Error accessing https://www.netflix.com, response code: 302 22 | Error accessing https://www.netflix.com, response code: 302 23 | Error accessing https://www.netflix.com, response code: 302 24 | Error accessing https://www.netflix.com, response code: 302 25 | Error accessing https://www.netflix.com, response code: 302 26 | Error accessing https://www.netflix.com, response code: 302 27 | Error accessing https://www.netflix.com, response code: 302 28 | Error accessing https://www.netflix.com, response code: 302 29 | Error accessing https://www.netflix.com, response code: 302 30 | Error accessing https://www.netflix.com, response code: 302 31 | Error accessing https://www.netflix.com, response code: 302 32 | Error accessing https://www.netflix.com, response code: 302 33 | Error accessing https://www.netflix.com, response code: 302 34 | Error accessing https://www.netflix.com, response code: 302 35 | Error accessing https://www.netflix.com, response code: 302 36 | Error accessing https://www.netflix.com, response code: 302 37 | Error accessing https://www.netflix.com, response code: 302 38 | Error accessing https://www.netflix.com, response code: 302 39 | Error accessing https://www.netflix.com, response code: 302 40 | Error accessing https://www.netflix.com, response code: 302 41 | Error accessing https://www.netflix.com, response code: 302 42 | Error accessing https://www.netflix.com, response code: 302 43 | Error accessing https://www.netflix.com, response code: 302 44 | Error accessing https://www.netflix.com, response code: 302 45 | Error accessing https://www.netflix.com, response code: 302 46 | Error accessing https://www.netflix.com, response code: 302 47 | Error accessing https://www.netflix.com, response code: 302 48 | Error accessing https://www.netflix.com, response code: 302 49 | Error accessing https://www.netflix.com, response code: 302 50 | Error accessing https://www.netflix.com, response code: 302 51 | Error accessing https://www.netflix.com, response code: 302 52 | Error accessing https://www.netflix.com, response code: 302 53 | Error accessing https://www.netflix.com, response code: 302 54 | Error accessing https://www.netflix.com, response code: 302 55 | Error accessing https://www.netflix.com, response code: 302 56 | Error accessing https://www.netflix.com, response code: 302 57 | Error accessing https://www.netflix.com, response code: 302 58 | Error accessing https://www.netflix.com, response code: 302 59 | Error accessing https://www.netflix.com, response code: 302 60 | Error accessing https://www.netflix.com, response code: 302 61 | Error accessing https://www.netflix.com, response code: 302 62 | Error accessing https://www.netflix.com, response code: 302 63 | Error accessing https://www.netflix.com, response code: 302 64 | Error accessing https://www.netflix.com, response code: 302 65 | Error accessing https://www.netflix.com, response code: 302 66 | Error accessing https://www.netflix.com, response code: 302 67 | Error accessing https://www.netflix.com, response code: 302 68 | Error accessing https://www.netflix.com, response code: 302 69 | Error accessing https://www.netflix.com, response code: 302 70 | Error accessing https://www.netflix.com, response code: 302 71 | Error accessing https://www.netflix.com, response code: 302 72 | Error accessing https://www.netflix.com, response code: 302 73 | Error accessing https://www.netflix.com, response code: 302 74 | Error accessing https://www.netflix.com, response code: 302 75 | Error accessing https://www.netflix.com, response code: 302 76 | Error accessing https://www.netflix.com, response code: 302 77 | Error accessing https://www.netflix.com, response code: 302 78 | Error accessing https://www.netflix.com, response code: 302 79 | Error accessing https://www.netflix.com, response code: 302 80 | Error accessing https://www.netflix.com, response code: 302 81 | Error accessing https://www.netflix.com, response code: 302 82 | Error accessing https://www.netflix.com, response code: 302 83 | Error accessing https://www.netflix.com, response code: 302 84 | Error accessing https://www.netflix.com, response code: 302 85 | Error accessing https://www.netflix.com, response code: 302 86 | Error accessing https://www.netflix.com, response code: 302 87 | Error accessing https://www.netflix.com, response code: 302 88 | Error accessing https://www.netflix.com, response code: 302 89 | Error accessing https://www.netflix.com, response code: 302 90 | Error accessing https://www.netflix.com, response code: 302 91 | Error accessing https://www.netflix.com, response code: 302 92 | Error accessing https://www.netflix.com, response code: 302 93 | Error accessing https://www.netflix.com, response code: 302 94 | Error accessing https://www.netflix.com, response code: 302 95 | Error accessing https://www.netflix.com, response code: 302 96 | Error accessing https://www.netflix.com, response code: 302 97 | Error accessing https://www.netflix.com, response code: 302 98 | Error accessing https://www.netflix.com, response code: 302 99 | Error accessing https://www.netflix.com, response code: 302 100 | Error accessing https://www.netflix.com, response code: 302 101 | Error accessing https://www.netflix.com, response code: 302 102 | Error accessing https://www.netflix.com, response code: 302 103 | Error accessing https://www.netflix.com, response code: 302 104 | Error accessing https://www.netflix.com, response code: 302 105 | Error accessing https://www.netflix.com, response code: 302 106 | Error accessing https://www.netflix.com, response code: 302 107 | Error accessing https://www.netflix.com, response code: 302 108 | Error accessing https://www.netflix.com, response code: 302 109 | Error accessing https://www.netflix.com, response code: 302 110 | Error accessing https://www.netflix.com, response code: 302 111 | Error accessing https://www.netflix.com, response code: 302 112 | Error accessing https://www.netflix.com, response code: 302 113 | Error accessing https://www.netflix.com, response code: 302 114 | Error accessing https://www.netflix.com, response code: 302 115 | Error accessing https://www.netflix.com, response code: 302 116 | Error accessing https://www.netflix.com, response code: 302 117 | Error accessing https://www.netflix.com, response code: 302 118 | Error accessing https://www.netflix.com, response code: 302 119 | Error accessing https://www.netflix.com, response code: 302 120 | Error accessing https://www.netflix.com, response code: 302 121 | Error accessing https://www.netflix.com, response code: 302 122 | Error accessing https://www.netflix.com, response code: 302 123 | Error accessing https://www.netflix.com, response code: 302 124 | Error accessing https://www.netflix.com, response code: 302 125 | Error accessing https://www.netflix.com, response code: 302 126 | Error accessing https://www.netflix.com, response code: 302 127 | Error accessing https://www.netflix.com, response code: 302 128 | Error accessing https://www.netflix.com, response code: 302 129 | Error accessing https://www.netflix.com, response code: 302 130 | Error accessing https://www.netflix.com, response code: 302 131 | Error accessing https://www.netflix.com, response code: 302 132 | Error accessing https://www.netflix.com, response code: 302 133 | Error accessing https://www.netflix.com, response code: 302 134 | Error accessing https://www.netflix.com, response code: 302 135 | Error accessing https://www.netflix.com, response code: 302 136 | Error accessing https://www.netflix.com, response code: 302 137 | Error accessing https://www.netflix.com, response code: 302 138 | Error accessing https://www.netflix.com, response code: 302 139 | Error accessing https://www.netflix.com, response code: 302 140 | Error accessing https://www.netflix.com, response code: 302 141 | Error accessing https://www.netflix.com, response code: 302 142 | Error accessing https://www.netflix.com, response code: 302 143 | Error accessing https://www.netflix.com, response code: 302 144 | Error accessing https://www.netflix.com, response code: 302 145 | Error accessing https://www.netflix.com, response code: 302 146 | Error accessing https://www.netflix.com, response code: 302 147 | Error accessing https://www.netflix.com, response code: 302 148 | Error accessing https://www.netflix.com, response code: 302 149 | Error accessing https://www.netflix.com, response code: 302 150 | Error accessing https://www.netflix.com, response code: 302 151 | Error accessing https://www.netflix.com, response code: 302 152 | Error accessing https://www.netflix.com, response code: 302 153 | Error accessing https://www.netflix.com, response code: 302 154 | Error accessing https://www.netflix.com, response code: 302 155 | Error accessing https://www.netflix.com, response code: 302 156 | Error accessing https://www.netflix.com, response code: 302 157 | Error accessing https://www.netflix.com, response code: 302 158 | Error accessing https://www.netflix.com, response code: 302 159 | Error accessing https://www.netflix.com, response code: 302 160 | Error accessing https://www.netflix.com, response code: 302 161 | Error accessing https://www.netflix.com, response code: 302 162 | Error accessing https://www.netflix.com, response code: 302 163 | Error accessing https://www.netflix.com, response code: 302 164 | Error accessing https://www.netflix.com, response code: 302 165 | Error accessing https://www.netflix.com, response code: 302 166 | Error accessing https://www.netflix.com, response code: 302 167 | Error accessing https://www.netflix.com, response code: 302 168 | Error accessing https://www.netflix.com, response code: 302 169 | Error accessing https://www.netflix.com, response code: 302 170 | Error accessing https://www.netflix.com, response code: 302 171 | Error accessing https://www.netflix.com, response code: 302 172 | Error accessing https://www.netflix.com, response code: 302 173 | Error accessing https://www.netflix.com, response code: 302 174 | Error accessing https://www.netflix.com, response code: 302 175 | Error accessing https://www.netflix.com, response code: 302 176 | Error accessing https://www.netflix.com, response code: 302 177 | Error accessing https://www.netflix.com, response code: 302 178 | Error accessing https://www.netflix.com, response code: 302 179 | Error accessing https://www.netflix.com, response code: 302 180 | Error accessing https://www.netflix.com, response code: 302 181 | Error accessing https://www.netflix.com, response code: 302 182 | Error accessing https://www.netflix.com, response code: 302 183 | Error accessing https://www.netflix.com, response code: 302 184 | Error accessing https://www.netflix.com, response code: 302 185 | Error accessing https://www.netflix.com, response code: 302 186 | Error accessing https://www.netflix.com, response code: 302 187 | Error accessing https://www.netflix.com, response code: 302 188 | Error accessing https://www.netflix.com, response code: 302 189 | Error accessing https://www.netflix.com, response code: 302 190 | Error accessing https://www.netflix.com, response code: 302 191 | Error accessing https://www.netflix.com, response code: 302 192 | Error accessing https://www.netflix.com, response code: 302 193 | Error accessing https://www.netflix.com, response code: 302 194 | Error accessing https://www.netflix.com, response code: 302 195 | Error accessing https://www.netflix.com, response code: 302 196 | Error accessing https://www.netflix.com, response code: 302 197 | Error accessing https://www.netflix.com, response code: 302 198 | Error accessing https://www.netflix.com, response code: 302 199 | Error accessing https://www.netflix.com, response code: 302 200 | Error accessing https://www.netflix.com, response code: 302 201 | Error accessing https://www.netflix.com, response code: 302 202 | Error accessing https://www.netflix.com, response code: 302 203 | Error accessing https://www.netflix.com, response code: 302 204 | Error accessing https://www.netflix.com, response code: 302 205 | Error accessing https://www.netflix.com, response code: 302 206 | Error accessing https://www.netflix.com, response code: 302 207 | Error accessing https://www.netflix.com, response code: 302 208 | Error accessing https://www.netflix.com, response code: 302 209 | Error accessing https://www.netflix.com, response code: 302 210 | Error accessing https://www.netflix.com, response code: 302 211 | Error accessing https://www.netflix.com, response code: 302 212 | Error accessing https://www.netflix.com, response code: 302 213 | Error accessing https://www.netflix.com, response code: 302 214 | Error accessing https://www.netflix.com, response code: 302 215 | Error accessing https://www.netflix.com, response code: 302 216 | Error accessing https://www.netflix.com, response code: 302 217 | Error accessing https://www.netflix.com, response code: 302 218 | Error accessing https://www.netflix.com, response code: 219 | Error accessing https://www.netflix.com, response code: 302 220 | Error accessing https://www.netflix.com, response code: 302 221 | Error accessing https://www.netflix.com, response code: 302 222 | Error accessing https://www.netflix.com, response code: 302 223 | Error accessing https://www.netflix.com, response code: 302 224 | Error accessing https://www.netflix.com, response code: 302 225 | Error accessing https://www.netflix.com, response code: 302 226 | Error accessing https://www.netflix.com, response code: 302 227 | Error accessing https://www.netflix.com, response code: 302 228 | Error accessing https://www.netflix.com, response code: 302 229 | Error accessing https://www.netflix.com, response code: 302 230 | Error accessing https://www.netflix.com, response code: 302 231 | Error accessing https://www.netflix.com, response code: 302 232 | Error accessing https://www.netflix.com, response code: 302 233 | Error accessing https://www.netflix.com, response code: 302 234 | Error accessing https://www.netflix.com, response code: 302 235 | Error accessing https://www.netflix.com, response code: 302 236 | Error accessing https://www.netflix.com, response code: 302 237 | Error accessing https://www.netflix.com, response code: 302 238 | Error accessing https://www.netflix.com, response code: 302 239 | Error accessing https://www.netflix.com, response code: 302 240 | Error accessing https://www.netflix.com, response code: 302 241 | Error accessing https://www.netflix.com, response code: 302 242 | Error accessing https://www.netflix.com, response code: 302 243 | Error accessing https://www.netflix.com, response code: 302 244 | Error accessing https://www.netflix.com, response code: 302 245 | Error accessing https://www.netflix.com, response code: 302 246 | Error accessing https://www.netflix.com, response code: 302 247 | Error accessing https://www.netflix.com, response code: 302 248 | Error accessing https://www.netflix.com, response code: 302 249 | Error accessing https://www.netflix.com, response code: 302 250 | Error accessing https://www.netflix.com, response code: 302 251 | Error accessing https://www.netflix.com, response code: 302 252 | Error accessing https://www.netflix.com, response code: 302 253 | Error accessing https://www.netflix.com, response code: 302 254 | Error accessing https://www.netflix.com, response code: 302 255 | Error accessing https://www.netflix.com, response code: 302 256 | Error accessing https://www.netflix.com, response code: 302 257 | Error accessing https://www.netflix.com, response code: 302 258 | Error accessing https://www.netflix.com, response code: 302 259 | Error accessing https://www.netflix.com, response code: 302 260 | Error accessing https://www.netflix.com, response code: 302 261 | Error accessing https://www.netflix.com, response code: 302 262 | Error accessing https://www.netflix.com, response code: 302 263 | Error accessing https://www.netflix.com, response code: 302 264 | Error accessing https://www.netflix.com, response code: 302 265 | Error accessing https://www.netflix.com, response code: 302 266 | Error accessing https://www.netflix.com, response code: 302 267 | Error accessing https://www.netflix.com, response code: 302 268 | Error accessing https://www.netflix.com, response code: 302 269 | Error accessing https://www.netflix.com, response code: 302 270 | Error accessing https://www.netflix.com, response code: 302 271 | Error accessing https://www.netflix.com, response code: 302 272 | Error accessing https://www.netflix.com, response code: 302 273 | Error accessing https://www.netflix.com, response code: 302 274 | Error accessing https://www.netflix.com, response code: 302 275 | Error accessing https://www.netflix.com, response code: 302 276 | Error accessing https://www.netflix.com, response code: 302 277 | Error accessing https://www.netflix.com, response code: 302 278 | Error accessing https://www.netflix.com, response code: 302 279 | Error accessing https://www.netflix.com, response code: 302 280 | Error accessing https://www.netflix.com, response code: 302 281 | Error accessing https://www.netflix.com, response code: 302 282 | Error accessing https://www.netflix.com, response code: 302 283 | Error accessing https://www.netflix.com, response code: 302 284 | Error accessing https://www.netflix.com, response code: 302 285 | Error accessing https://www.netflix.com, response code: 302 286 | Error accessing https://www.netflix.com, response code: 302 287 | Error accessing https://www.netflix.com, response code: 302 288 | Error accessing https://www.netflix.com, response code: 302 289 | Error accessing https://www.netflix.com, response code: 302 290 | Error accessing https://www.netflix.com, response code: 302 291 | Error accessing https://www.netflix.com, response code: 302 292 | Error accessing https://www.netflix.com, response code: 302 293 | Error accessing https://www.netflix.com, response code: 302 294 | Error accessing https://www.netflix.com, response code: 302 295 | Error accessing https://www.netflix.com, response code: 302 296 | Error accessing https://www.netflix.com, response code: 302 297 | Error accessing https://www.netflix.com, response code: 302 298 | Error accessing https://www.netflix.com, response code: 302 299 | Error accessing https://www.netflix.com, response code: 302 300 | Error accessing https://www.netflix.com, response code: 302 301 | Error accessing https://www.netflix.com, response code: 302 302 | Error accessing https://www.netflix.com, response code: 302 303 | Error accessing https://www.netflix.com, response code: 302 304 | Error accessing https://www.netflix.com, response code: 302 305 | Error accessing https://www.netflix.com, response code: 302 306 | Error accessing https://www.netflix.com, response code: 302 307 | Error accessing https://www.netflix.com, response code: 302 308 | Error accessing https://www.netflix.com, response code: 302 309 | Error accessing https://www.netflix.com, response code: 302 310 | Error accessing https://www.netflix.com, response code: 302 311 | Error accessing https://www.netflix.com, response code: 302 312 | Error accessing https://www.netflix.com, response code: 302 313 | Error accessing https://www.netflix.com, response code: 302 314 | Error accessing https://www.netflix.com, response code: 302 315 | Error accessing https://www.netflix.com, response code: 302 316 | Error accessing https://www.netflix.com, response code: 302 317 | Error accessing https://www.netflix.com, response code: 302 318 | Error accessing https://www.netflix.com, response code: 302 319 | Error accessing https://www.netflix.com, response code: 302 320 | Error accessing https://www.netflix.com, response code: 302 321 | Error accessing https://www.netflix.com, response code: 302 322 | Error accessing https://www.netflix.com, response code: 302 323 | Error accessing https://www.netflix.com, response code: 302 324 | Error accessing https://www.netflix.com, response code: 302 325 | Error accessing https://www.netflix.com, response code: 302 326 | Error accessing https://www.netflix.com, response code: 302 327 | Error accessing https://www.netflix.com, response code: 302 328 | Error accessing https://www.netflix.com, response code: 302 329 | Error accessing https://www.netflix.com, response code: 302 330 | Error accessing https://www.netflix.com, response code: 302 331 | Error accessing https://www.netflix.com, response code: 302 332 | Error accessing https://www.netflix.com, response code: 302 333 | Error accessing https://www.netflix.com, response code: 302 334 | Error accessing https://www.netflix.com, response code: 302 335 | Error accessing https://www.netflix.com, response code: 302 336 | Error accessing https://www.netflix.com, response code: 302 337 | Error accessing https://www.netflix.com, response code: 302 338 | Error accessing https://www.netflix.com, response code: 302 339 | Error accessing https://www.netflix.com, response code: 302 340 | Error accessing https://www.netflix.com, response code: 302 341 | Error accessing https://www.netflix.com, response code: 302 342 | Error accessing https://www.netflix.com, response code: 302 343 | Error accessing https://www.netflix.com, response code: 302 344 | Error accessing https://www.netflix.com, response code: 302 345 | Error accessing https://www.netflix.com, response code: 302 346 | Error accessing https://www.netflix.com, response code: 302 347 | Error accessing https://www.netflix.com, response code: 302 348 | Error accessing https://www.netflix.com, response code: 302 349 | Error accessing https://www.netflix.com, response code: 302 350 | Error accessing https://www.netflix.com, response code: 302 351 | Error accessing https://www.netflix.com, response code: 352 | Error accessing https://www.netflix.com, response code: 302 353 | Error accessing https://www.netflix.com, response code: 302 354 | Error accessing https://www.netflix.com, response code: 302 355 | Error accessing https://www.netflix.com, response code: 302 356 | Error accessing https://www.netflix.com, response code: 302 357 | Error accessing https://www.netflix.com, response code: 302 358 | Error accessing https://www.netflix.com, response code: 302 359 | Error accessing https://www.netflix.com, response code: 302 360 | Error accessing https://www.netflix.com, response code: 302 361 | Error accessing https://www.netflix.com, response code: 302 362 | Error accessing https://www.netflix.com, response code: 302 363 | Error accessing https://www.netflix.com, response code: 302 364 | Error accessing https://www.netflix.com, response code: 302 365 | Error accessing https://www.netflix.com, response code: 302 366 | Error accessing https://www.netflix.com, response code: 302 367 | Error accessing https://www.netflix.com, response code: 302 368 | Error accessing https://www.netflix.com, response code: 369 | Error accessing https://www.netflix.com, response code: 370 | Error accessing https://www.netflix.com, response code: 371 | Error accessing https://www.netflix.com, response code: 372 | Error accessing https://www.netflix.com, response code: 373 | Error accessing https://www.netflix.com, response code: 374 | Error accessing https://www.netflix.com, response code: 302 375 | Error accessing https://www.netflix.com, response code: 302 376 | Error accessing https://www.netflix.com, response code: 302 377 | Error accessing https://www.netflix.com, response code: 302 378 | Error accessing https://www.netflix.com, response code: 379 | Error accessing https://www.netflix.com, response code: 380 | Error accessing https://www.netflix.com, response code: 381 | Error accessing https://www.netflix.com, response code: 382 | Error accessing https://www.netflix.com, response code: 383 | Error accessing https://www.netflix.com, response code: 302 384 | Error accessing https://www.netflix.com, response code: 302 385 | Error accessing https://www.netflix.com, response code: 302 386 | Error accessing https://www.netflix.com, response code: 302 387 | Error accessing https://www.netflix.com, response code: 302 388 | Error accessing https://www.netflix.com, response code: 302 389 | Error accessing https://www.netflix.com, response code: 302 390 | Error accessing https://www.netflix.com, response code: 302 391 | Error accessing https://www.netflix.com, response code: 392 | Error accessing https://www.netflix.com, response code: 393 | Error accessing https://www.netflix.com, response code: 394 | Error accessing https://www.netflix.com, response code: 395 | Error accessing https://www.netflix.com, response code: 302 396 | Error accessing https://www.netflix.com, response code: 302 397 | Error accessing https://www.netflix.com, response code: 302 398 | Error accessing https://www.netflix.com, response code: 302 399 | Error accessing https://www.netflix.com, response code: 302 400 | Error accessing https://www.netflix.com, response code: 302 401 | Error accessing https://www.netflix.com, response code: 302 402 | Error accessing https://www.netflix.com, response code: 302 403 | -------------------------------------------------------------------------------- /logs/netlify_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://app.netlify.com, response code: 2 | -------------------------------------------------------------------------------- /logs/popular_report.log: -------------------------------------------------------------------------------- 1 | 2024-11-06 15:11, success 2 | -------------------------------------------------------------------------------- /logs/spotify_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing , response code: 000 2 | Error accessing , response code: 000 3 | Error accessing , response code: 000 4 | Error accessing , response code: 000 5 | Error accessing https://www.spotify.com, response code: 6 | Error accessing https://www.spotify.com, response code: 000 7 | Error accessing https://www.spotify.com, response code: 8 | Error accessing https://www.spotify.com, response code: 9 | Error accessing https://www.spotify.com, response code: 10 | Error accessing https://www.spotify.com, response code: 11 | Error accessing https://www.spotify.com, response code: 12 | Error accessing https://www.spotify.com, response code: 13 | Error accessing https://www.spotify.com, response code: 502 14 | Error accessing https://www.spotify.com, response code: 15 | Error accessing https://www.spotify.com, response code: 502 16 | Error accessing https://www.spotify.com, response code: 17 | Error accessing https://www.spotify.com, response code: 18 | Error accessing https://www.spotify.com, response code: 000 19 | Error accessing https://www.spotify.com, response code: 20 | Error accessing https://www.spotify.com, response code: 21 | Error accessing https://www.spotify.com, response code: 22 | Error accessing https://www.spotify.com, response code: 000 23 | -------------------------------------------------------------------------------- /logs/twitter_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.twitter.com, response code: 000 2 | Error accessing https://www.twitter.com, response code: 000 3 | Error accessing https://www.twitter.com, response code: 000 4 | Error accessing https://www.twitter.com, response code: 000 5 | Error accessing https://www.twitter.com, response code: 000 6 | Error accessing https://www.twitter.com, response code: 000 7 | -------------------------------------------------------------------------------- /logs/vercel_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://vercel.com, response code: 2 | Error accessing https://vercel.com, response code: 3 | -------------------------------------------------------------------------------- /logs/websites_errors.log: -------------------------------------------------------------------------------- 1 | Error accessing https://www.reddit.com, response code: 403 2 | Error accessing https://www.reddit.com, response code: 403 3 | Error accessing https://www.reddit.com, response code: 403 4 | Error accessing https://www.reddit.com, response code: 403 5 | -------------------------------------------------------------------------------- /logs/websites_report.log: -------------------------------------------------------------------------------- 1 | 2024-11-06 15:11, failed 2 | -------------------------------------------------------------------------------- /main.js: -------------------------------------------------------------------------------- 1 | /* This is the maximum number of days that will be displayed in the report. */ 2 | const maxDays = 30; 3 | 4 | /** 5 | * It fetches a log file, normalizes the data, and then constructs a status stream. 6 | * @param container - the div element that will contain the status stream 7 | * @param key - the key of the report 8 | * @param url - The URL of the website to be tested 9 | */ 10 | async function genReportLog(container, key, url) { 11 | const response = await fetch("logs/" + key + "_report.log"); 12 | let statusLines = ""; 13 | if (response.ok) { 14 | statusLines = await response.text(); 15 | } 16 | 17 | const normalized = normalizeData(statusLines); 18 | const statusStream = constructStatusStream(key, url, normalized); 19 | container.appendChild(statusStream); 20 | } 21 | 22 | /** 23 | * It takes a key, a url, and an array of uptime data, and returns a DOM element that contains a status 24 | * stream. 25 | * @param key - The name of the service 26 | * @param url - the url of the website 27 | * @param uptimeData - an array of objects, each object has a "status" property, which is either "up" 28 | * or "down" 29 | * @returns A DOM element. 30 | */ 31 | function constructStatusStream(key, url, uptimeData) { 32 | let streamContainer = templatize("statusStreamContainerTemplate"); 33 | for (var ii = maxDays - 1; ii >= 0; ii--) { 34 | let line = constructStatusLine(key, ii, uptimeData[ii]); 35 | streamContainer.appendChild(line); 36 | } 37 | 38 | const lastSet = uptimeData[0]; 39 | const color = getColor(lastSet); 40 | 41 | const container = templatize("statusContainerTemplate", { 42 | title: key, 43 | url: url, 44 | color: color, 45 | status: getStatusText(color), 46 | upTime: uptimeData.upTime, 47 | }); 48 | 49 | container.appendChild(streamContainer); 50 | return container; 51 | } 52 | 53 | /** 54 | * It takes a key, a relative day, and an array of up times and returns a status square. 55 | * @param key - the key of the object in the array 56 | * @param relDay - The number of days ago the date is. 57 | * @param upTimeArray - [{date: "2019-01-01", upTime: "100"}, {date: "2019-01-02", upTime: "100"}, 58 | * {date: "2019-01-03", upTime: "100"}, {date: "2019-01-04", up 59 | * @returns A string of HTML code. 60 | */ 61 | function constructStatusLine(key, relDay, upTimeArray) { 62 | let date = new Date(); 63 | date.setDate(date.getDate() - relDay); 64 | 65 | return constructStatusSquare(key, date, upTimeArray); 66 | } 67 | 68 | /** 69 | * If the uptime value is null, return "nodata"; if it's 1, return "success"; if it's less than 0.3, 70 | * return "failure"; otherwise, return "partial" 71 | * @param uptimeVal - The uptime value for the current row. 72 | * @returns a string. 73 | */ 74 | function getColor(uptimeVal) { 75 | return uptimeVal == null 76 | ? "nodata" 77 | : uptimeVal == 1 78 | ? "success" 79 | : uptimeVal < 0.3 80 | ? "failure" 81 | : "partial"; 82 | } 83 | 84 | /** 85 | * It creates a square with a tooltip 86 | * @param key - the key of the object in the data array 87 | * @param date - "2020-01-01" 88 | * @param uptimeVal - a number between 0 and 1 89 | * @returns A function that takes in a key, date, and uptimeVal. 90 | */ 91 | function constructStatusSquare(key, date, uptimeVal) { 92 | const color = getColor(uptimeVal); 93 | let square = templatize("statusSquareTemplate", { 94 | color: color, 95 | tooltip: getTooltip(key, date, color), 96 | }); 97 | 98 | const show = () => { 99 | showTooltip(square, key, date, color); 100 | }; 101 | square.addEventListener("mouseover", show); 102 | square.addEventListener("mousedown", show); 103 | square.addEventListener("mouseout", hideTooltip); 104 | return square; 105 | } 106 | 107 | /* A variable that is used to generate unique IDs for the cloned elements. */ 108 | let cloneId = 0; 109 | 110 | /** 111 | * It takes a template element and a set of parameters, and returns a clone of the template element 112 | * with the parameters applied. 113 | * 114 | * The function is pretty simple. It takes a template element and a set of parameters, and returns a 115 | * clone of the template element with the parameters applied. 116 | * 117 | * The first thing it does is clone the template element. This is important because we don't want to 118 | * modify the original template element. 119 | * 120 | * Next, it checks to see if there are any parameters. If there aren't, it just returns the clone. 121 | * 122 | * If there are parameters, it calls applyTemplateSubstitutions to apply the parameters to the clone. 123 | * 124 | * Finally, it returns the clone. 125 | * @param templateId - The id of the template to clone. 126 | * @param parameters - { 127 | * @returns A clone of the template with the id of the template and the parameters applied. 128 | */ 129 | function templatize(templateId, parameters) { 130 | let clone = document.getElementById(templateId).cloneNode(true); 131 | clone.id = "template_clone_" + cloneId++; 132 | if (!parameters) { 133 | return clone; 134 | } 135 | 136 | applyTemplateSubstitutions(clone, parameters); 137 | return clone; 138 | } 139 | 140 | /** 141 | * It takes a DOM node and a set of parameters, and it replaces all the template strings in the node 142 | * with the values from the parameters. 143 | * 144 | * The function is recursive, so it will work on any node, and it will work on all the child nodes of 145 | * that node. 146 | * 147 | * The function is also smart enough to know that if a node has no child nodes, then it should replace 148 | * the innerText of the node. 149 | * 150 | * The function is also smart enough to know that if a node has child nodes, then it should recursively 151 | * call itself on each of the child nodes. 152 | * 153 | * The function is also smart enough to know that it should replace template strings in the attributes 154 | * of the node. 155 | * 156 | * The function is also smart enough to know that it should replace template strings in the innerText 157 | * of the node. 158 | * 159 | * The function is also smart enough to know that it should replace template strings in 160 | * @param node - the node to apply the template substitutions to 161 | * @param parameters - { 162 | */ 163 | function applyTemplateSubstitutions(node, parameters) { 164 | const attributes = node.getAttributeNames(); 165 | for (var ii = 0; ii < attributes.length; ii++) { 166 | const attr = attributes[ii]; 167 | const attrVal = node.getAttribute(attr); 168 | node.setAttribute(attr, templatizeString(attrVal, parameters)); 169 | } 170 | 171 | if (node.childElementCount == 0) { 172 | node.innerText = templatizeString(node.innerText, parameters); 173 | } else { 174 | const children = Array.from(node.children); 175 | children.forEach((n) => { 176 | applyTemplateSubstitutions(n, parameters); 177 | }); 178 | } 179 | } 180 | 181 | /** 182 | * It takes a string and replaces all instances of `` with the value of `parameters[key]`. 183 | * 184 | * Here's an example of how to use it: 185 | * @param text - The string to be templatized. 186 | * @param parameters - { 187 | * @returns The text with the parameters replaced. 188 | */ 189 | function templatizeString(text, parameters) { 190 | if (parameters) { 191 | for (const [key, val] of Object.entries(parameters)) { 192 | text = text.replaceAll("$" + key, val); 193 | } 194 | } 195 | return text; 196 | } 197 | 198 | /** 199 | * If the color is "nodata", return "No Data Available", else if the color is "success", return "Fully 200 | * Operational", else if the color is "failure", return "Major Outage", else if the color is "partial", 201 | * return "Partial Outage", else return "Unknown" 202 | * @param color - The color of the status indicator. 203 | * @returns the value of the variable "color" 204 | */ 205 | function getStatusText(color) { 206 | if (color === "nodata") { 207 | return "No Data Available"; 208 | } else if (color === "success") { 209 | return "Fully Operational"; 210 | } else if (color === "failure") { 211 | return "Major Outage"; 212 | } else if (color === "partial") { 213 | return "Partial Outage"; 214 | } else { 215 | return "Unknown"; 216 | } 217 | } 218 | 219 | /** 220 | * If the color is "nodata", return "No Data Available: Health check was not performed.". Otherwise, if 221 | * the color is "success", return "No downtime recorded on this day.". Otherwise, if the color is 222 | * "failure", return "Major outages recorded on this day.". Otherwise, if the color is "partial", 223 | * return "Partial outages recorded on this day.". Otherwise, return "Unknown" 224 | * @param color - The color of the cell. 225 | * @returns the value of the variable color. 226 | */ 227 | function getStatusDescriptiveText(color) { 228 | return color == "nodata" 229 | ? "No Data Available: Health check was not performed." 230 | : color == "success" 231 | ? "No downtime recorded on this day." 232 | : color == "failure" 233 | ? "Major outages recorded on this day." 234 | : color == "partial" 235 | ? "Partial outages recorded on this day." 236 | : "Unknown"; 237 | } 238 | 239 | /** 240 | * It takes a key, a date, a quartile, and a color, and returns a string that looks like this: "key | 241 | * date : quartile : statusText" 242 | * @param key - The key of the data point. 243 | * @param date - The date of the data point 244 | * @param quartile - The quartile value of the data point. 245 | * @param color - the color of the bar 246 | * @returns A string. 247 | */ 248 | function getTooltip(key, date, quartile, color) { 249 | let statusText = getStatusText(color); 250 | return `${key} | ${date.toDateString()} : ${quartile} : ${statusText}`; 251 | } 252 | 253 | /** 254 | * Create a new element with the given tag and class name. 255 | * @param tag - The tag name of the element you want to create. 256 | * @param className - The class name of the element you want to create. 257 | * @returns the element. 258 | */ 259 | function create(tag, className) { 260 | let element = document.createElement(tag); 261 | element.className = className; 262 | return element; 263 | } 264 | 265 | /** 266 | * It takes a string of data, splits it into rows, splits the rows into days, averages the data for 267 | * each day, and returns an object with the average data for each day. 268 | * @param statusLines - The output of the command 269 | * @returns An object with the following structure: 270 | * { 271 | * "0": { 272 | * "cpu": "0.00", 273 | * "mem": "0.00", 274 | * "net": "0.00" 275 | * }, 276 | * "1": { 277 | * "cpu": "0.00", 278 | * "mem": "0.00", 279 | * "net": " 280 | */ 281 | function normalizeData(statusLines) { 282 | const rows = statusLines.split("\n"); 283 | const dateNormalized = splitRowsByDate(rows); 284 | 285 | let relativeDateMap = {}; 286 | const now = Date.now(); 287 | for (const [key, val] of Object.entries(dateNormalized)) { 288 | if (key == "upTime") { 289 | continue; 290 | } 291 | 292 | const relDays = getRelativeDays(now, new Date(key).getTime()); 293 | relativeDateMap[relDays] = getDayAverage(val); 294 | } 295 | 296 | relativeDateMap.upTime = dateNormalized.upTime; 297 | return relativeDateMap; 298 | } 299 | 300 | /** 301 | * If the value is not null or empty, return the average of the values in the array. 302 | * @param val - The array of values to be averaged. 303 | * @returns The average of the values in the array. 304 | */ 305 | function getDayAverage(val) { 306 | if (!val || val.length == 0) { 307 | return null; 308 | } else { 309 | return val.reduce((a, v) => a + v) / val.length; 310 | } 311 | } 312 | 313 | /** 314 | * It takes two dates and returns the number of days between them 315 | * @param date1 - The date you want to compare to. 316 | * @param date2 - The date to compare to. 317 | * @returns The number of days between the two dates. 318 | */ 319 | function getRelativeDays(date1, date2) { 320 | return Math.floor(Math.abs((date1 - date2) / (24 * 3600 * 1000))); 321 | } 322 | 323 | /** 324 | * It takes a list of strings, each of which is a date and a result, and returns an object with the 325 | * results grouped by date. 326 | * 327 | * The function is called like this: 328 | * @param rows - an array of strings, each string is a row of data 329 | * @returns An object with the following properties: 330 | */ 331 | function splitRowsByDate(rows) { 332 | let dateValues = {}; 333 | let sum = 0, 334 | count = 0; 335 | for (var ii = 0; ii < rows.length; ii++) { 336 | const row = rows[ii]; 337 | if (!row) { 338 | continue; 339 | } 340 | 341 | const [dateTimeStr, resultStr] = row.split(",", 2); 342 | const dateTime = new Date( 343 | Date.parse(dateTimeStr.replace(/-/g, "/") + " GMT") 344 | ); 345 | const dateStr = dateTime.toDateString(); 346 | 347 | let resultArray = dateValues[dateStr]; 348 | if (!resultArray) { 349 | resultArray = []; 350 | dateValues[dateStr] = resultArray; 351 | if (dateValues.length > maxDays) { 352 | break; 353 | } 354 | } 355 | 356 | let result = 0; 357 | if (resultStr.trim() == "success") { 358 | result = 1; 359 | } 360 | sum += result; 361 | count++; 362 | 363 | resultArray.push(result); 364 | } 365 | 366 | const upTime = count ? ((sum / count) * 100).toFixed(2) + "%" : "--%"; 367 | dateValues.upTime = upTime; 368 | return dateValues; 369 | } 370 | 371 | /* Declaring a variable called tooltipTimeout and assigning it the value of null. */ 372 | let tooltipTimeout = null; 373 | 374 | /** 375 | * It takes in an element, a key, a date, and a color, and then it sets the inner text of the 376 | * tooltipDateTime element to the date, the inner text of the tooltipDescription element to the color, 377 | * the inner text of the tooltipStatus element to the color, and the class of the tooltipStatus element 378 | * to the color. 379 | * 380 | * Then it sets the top of the toolTipDiv element to the offsetTop of the element plus the offsetHeight 381 | * of the element plus 10, and the left of the toolTipDiv element to the offsetLeft of the element plus 382 | * the offsetWidth of the element divided by 2 minus the offsetWidth of the toolTipDiv element divided 383 | * by 2. 384 | * 385 | * Then it sets the opacity of the toolTipDiv element to 1. 386 | * @param element - the element that the mouse is over 387 | * @param key - the key of the data point 388 | * @param date - the date of the event 389 | * @param color - the color of the status 390 | */ 391 | function showTooltip(element, key, date, color) { 392 | clearTimeout(tooltipTimeout); 393 | const toolTipDiv = document.getElementById("tooltip"); 394 | 395 | document.getElementById("tooltipDateTime").innerText = date.toDateString(); 396 | document.getElementById("tooltipDescription").innerText = 397 | getStatusDescriptiveText(color); 398 | 399 | const statusDiv = document.getElementById("tooltipStatus"); 400 | statusDiv.innerText = getStatusText(color); 401 | statusDiv.className = color; 402 | 403 | toolTipDiv.style.top = element.offsetTop + element.offsetHeight + 10; 404 | toolTipDiv.style.left = 405 | element.offsetLeft + element.offsetWidth / 2 - toolTipDiv.offsetWidth / 2; 406 | toolTipDiv.style.opacity = "1"; 407 | } 408 | 409 | /** 410 | * If the user hovers over the tooltip, don't hide it. If the user doesn't hover over the tooltip, hide 411 | * it after 1 second. 412 | */ 413 | function hideTooltip() { 414 | tooltipTimeout = setTimeout(() => { 415 | const toolTipDiv = document.getElementById("tooltip"); 416 | toolTipDiv.style.opacity = "0"; 417 | }, 1000); 418 | } 419 | 420 | /** 421 | * It reads a configuration file, then for each line in the configuration file, it calls a function to 422 | * generate a report. 423 | * 424 | * The configuration file is a simple text file with one line per report. Each line has a key and a URL 425 | * separated by an equals sign. The key is used to name the report. The URL is used to fetch the 426 | * report. 427 | * 428 | * The function genReportLog() is called for each line in the configuration file. It takes three 429 | * parameters: 430 | * 431 | * The first parameter is the HTML element where the report will be placed. 432 | * The second parameter is the key from the configuration file. 433 | * The third parameter is the URL from the configuration file. 434 | * The function genReportLog() calls the function genReport() to generate the report. 435 | * 436 | * The function genReport() takes three parameters: 437 | * 438 | * The first parameter is the HTML element where the report will be placed. 439 | */ 440 | async function genAllReports() { 441 | const response = await fetch("urls.cfg"); 442 | const configText = await response.text(); 443 | const configLines = configText.split("\n"); 444 | for (let ii = 0; ii < configLines.length; ii++) { 445 | const configLine = configLines[ii]; 446 | const [key, url] = configLine.split("="); 447 | if (!key || !url) { 448 | continue; 449 | } 450 | 451 | await genReportLog(document.getElementById("reports"), key, url); 452 | } 453 | } 454 | 455 | /** 456 | * It fetches the contents of the incident report from the Cloudflare Worker, sanitizes the markdown, 457 | * and then inserts it into the HTML 458 | */ 459 | async function genIncidentReport() { 460 | const response = await fetch( 461 | "https://incidents.statsig.workers.dev/contents" 462 | ); 463 | if (response.ok) { 464 | const json = await response.json(); 465 | try { 466 | const activeDom = DOMPurify.sanitize( 467 | marked.parse(json.active ? json.active : "No active Incidents") 468 | ); 469 | const inactiveDom = DOMPurify.sanitize(marked.parse(json.inactive)); 470 | 471 | document.getElementById("activeIncidentReports").innerHTML = activeDom; 472 | document.getElementById("pastIncidentReports").innerHTML = inactiveDom; 473 | } catch (e) { 474 | console.log(e.message); 475 | } 476 | } 477 | } 478 | -------------------------------------------------------------------------------- /style.css: -------------------------------------------------------------------------------- 1 | * { 2 | box-sizing: border-box; 3 | } 4 | 5 | html { 6 | height: 100%; 7 | display: flex; 8 | flex-direction: column; 9 | } 10 | body { 11 | background-color: #f5f6f8; 12 | color: #3b3b3b; 13 | font-size: 14px; 14 | font-weight: 300; 15 | font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "Roboto", 16 | "Helvetica Neue", "Ubuntu", sans-serif; 17 | justify-content: center; 18 | line-height: 22px; 19 | margin: 0; 20 | padding: 0; 21 | text-align: center; 22 | transition: opacity 0.3s; 23 | } 24 | hr { 25 | margin: 20px 0; 26 | border: 0; 27 | border-bottom: solid 1px #ddd; 28 | } 29 | h1, 30 | h2, 31 | h3, 32 | h4, 33 | h5, 34 | h6, 35 | button, 36 | footer, 37 | input, 38 | textarea, 39 | .copyright, 40 | .button { 41 | font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", "Roboto", 42 | "Helvetica Neue", "Ubuntu", sans-serif; 43 | line-height: 125%; 44 | } 45 | 46 | h1 { 47 | color: #3b3b3b; 48 | font-size: 32px; 49 | font-weight: bold; 50 | margin: 0px; 51 | } 52 | h2 { 53 | color: #3b3b3b; 54 | font-size: 28px; 55 | font-weight: bold; 56 | margin: 16px 0 8px 0; 57 | } 58 | h3 { 59 | color: #3b3b3b; 60 | font-size: 24px; 61 | font-weight: 700; 62 | margin: 8px 0 4px 0; 63 | } 64 | h4 { 65 | color: #3b3b3b; 66 | font-size: 18px; 67 | font-weight: 600; 68 | margin-top: 5px; 69 | margin-bottom: 4px; 70 | } 71 | h5 { 72 | color: #3b3b3b; 73 | font-size: 16px; 74 | font-weight: bold; 75 | margin-top: 5px; 76 | margin-bottom: 4px; 77 | } 78 | h6 { 79 | color: #3b3b3b; 80 | font-size: 16px; 81 | font-weight: bold; 82 | margin-top: 5px; 83 | margin-bottom: 4px; 84 | } 85 | a { 86 | color: #194b7d; 87 | text-decoration: none; 88 | } 89 | 90 | .outlineButton, 91 | .button, 92 | button { 93 | background-color: #194b7d; 94 | border: none; 95 | border-radius: 8px; 96 | color: white; 97 | cursor: pointer; 98 | font-size: 16px; 99 | font-weight: 600; 100 | padding: 10px 16px; 101 | white-space: nowrap; 102 | } 103 | 104 | footer { 105 | color: #9c9c9c; 106 | margin: 40px; 107 | } 108 | 109 | footer a { 110 | font-weight: bold; 111 | } 112 | 113 | .pageContainer { 114 | padding: 30px 50px; 115 | background-color: #fff; 116 | box-shadow: 0px 6px 18px rgba(0, 0, 0, 0.06); 117 | border-radius: 5px; 118 | max-width: 900px; 119 | width: 100%; 120 | margin: 96px auto; 121 | } 122 | 123 | .headline { 124 | display: flex; 125 | align-items: center; 126 | justify-content: center; 127 | } 128 | 129 | .headline span { 130 | background-color: #f5f6f8; 131 | border-radius: 5px; 132 | padding: 6px; 133 | margin-left: 12px; 134 | font-size: 16px; 135 | font-weight: 700; 136 | text-transform: uppercase; 137 | } 138 | 139 | .reportContainer, 140 | .incidentsContainer { 141 | margin: 30px auto; 142 | width: 100%; 143 | } 144 | 145 | .statusContainer { 146 | border: 1px solid #ededed; 147 | border-radius: 5px; 148 | padding-top: 20px; 149 | text-align: left; 150 | padding: 24px; 151 | } 152 | 153 | .statusContainer + .statusContainer { 154 | border-top: 1px solid #eee; 155 | margin-top: 30px; 156 | } 157 | 158 | .statusStreamContainer { 159 | display: flex; 160 | justify-content: space-between; 161 | } 162 | 163 | .statusSquare { 164 | border-radius: 3px; 165 | height: 30px; 166 | min-width: 8px; 167 | width: 100%; 168 | } 169 | 170 | .statusSquare + .statusSquare { 171 | margin-left: 6px; 172 | } 173 | 174 | .sectionUrl { 175 | font-size: 14px; 176 | } 177 | 178 | .statusTitle { 179 | text-transform: uppercase; 180 | } 181 | 182 | .statusHeader { 183 | display: flex; 184 | flex-direction: row; 185 | align-items: center; 186 | margin-bottom: 2px; 187 | } 188 | 189 | .statusSubtitle { 190 | display: flex; 191 | flex-direction: row; 192 | align-items: center; 193 | margin-bottom: 12px; 194 | } 195 | 196 | .statusHeadline { 197 | color: #eee; 198 | padding: 4px 8px; 199 | border-radius: 15px; 200 | font-size: 12px; 201 | font-weight: 700; 202 | margin-left: 12px; 203 | } 204 | 205 | .statusUptime { 206 | flex: 1; 207 | text-align: right; 208 | color: #7c7c7c; 209 | font-size: 12px; 210 | } 211 | 212 | .uptimeContainer { 213 | color: #999; 214 | display: flex; 215 | margin-top: 8px; 216 | font-size: 12px; 217 | } 218 | 219 | .uptimeContainer hr { 220 | border: none; 221 | border-top: 1px dashed #eee; 222 | width: 100%; 223 | margin: 10px; 224 | } 225 | 226 | .success { 227 | background-color: #4cae50; 228 | color: #fff; 229 | } 230 | 231 | .failure { 232 | background-color: #f44336; 233 | color: #fff; 234 | } 235 | 236 | .nodata { 237 | background-color: #f8f8f8; 238 | color: #ccc; 239 | } 240 | 241 | .partial { 242 | background-color: #ff9800; 243 | color: #fff; 244 | } 245 | 246 | .tooltip { 247 | background-color: #fff; 248 | box-shadow: 0px 6px 18px rgba(0, 0, 0, 0.12); 249 | border-radius: 4px; 250 | color: #3b3b3b; 251 | font-size: 12px; 252 | line-height: 18px; 253 | padding: 16px; 254 | position: absolute; 255 | text-align: left; 256 | z-index: 100; 257 | width: 240px; 258 | transition: opacity 0.2s; 259 | } 260 | 261 | .tooltip .tooltipArrow { 262 | position: absolute; 263 | bottom: 100%; 264 | width: 4px; 265 | text-align: center; 266 | border: 4px solid transparent; 267 | border-bottom-color: #fff; 268 | left: 50%; 269 | margin-left: -2px; 270 | } 271 | 272 | .tooltip .tooltipDateTime { 273 | font-size: 12px; 274 | color: #7c7c7c; 275 | text-transform: uppercase; 276 | font-weight: 600; 277 | } 278 | 279 | .tooltip .tooltipKey { 280 | color: #ccc; 281 | font-size: 10px; 282 | } 283 | 284 | .tooltip .tooltipDescription { 285 | margin-top: 12px; 286 | font-size: 14px; 287 | color: #181818; 288 | } 289 | 290 | .tooltip #tooltipStatus { 291 | padding: 4px 8px; 292 | border-radius: 15px; 293 | font-size: 12px; 294 | font-weight: bold; 295 | margin-top: 6px; 296 | display: inline-block; 297 | } 298 | 299 | .tooltip hr { 300 | border: none; 301 | border-top: 1px solid #ededed; 302 | margin-top: 16px; 303 | } 304 | 305 | .incidentsContainer { 306 | background-color: #fafafa; 307 | } 308 | 309 | .incidentReportsHeader { 310 | margin-bottom: 30px; 311 | } 312 | 313 | @media screen and (max-width: 800px) { 314 | .pageContainer { 315 | padding: 30px 20px; 316 | margin: 0 auto 40px auto; 317 | } 318 | 319 | .statusHeader, 320 | .statusSubtitle { 321 | display: block; 322 | } 323 | 324 | .statusHeadline, 325 | .sectionUrl, 326 | .statusUptime { 327 | margin-left: 0; 328 | margin-top: 8px; 329 | text-align: left; 330 | } 331 | 332 | .statusTitle, 333 | .statusHeadline { 334 | display: inline-block; 335 | } 336 | 337 | .statusSquare + .statusSquare { 338 | margin-left: 0px; 339 | } 340 | 341 | .statusSquare { 342 | min-width: 4px; 343 | width: 100%; 344 | max-width: calc(10% - 4.5px); 345 | } 346 | 347 | .statusStreamContainer { 348 | flex-wrap: wrap; 349 | row-gap: 5px; 350 | column-gap: 5px; 351 | } 352 | } 353 | -------------------------------------------------------------------------------- /urls.cfg: -------------------------------------------------------------------------------- 1 | google=https://www.google.com 2 | facebook=https://www.facebook.com 3 | twitter=https://www.twitter.com 4 | instagram=https://www.instagram.com 5 | vercel=https://vercel.com 6 | netlify=https://app.netlify.com 7 | youtube=https://www.youtube.com 8 | linkedin=https://www.linkedin.com 9 | github=https://www.github.com 10 | reddit=https://www.reddit.com 11 | wikipedia=https://www.wikipedia.org 12 | amazon=https://www.amazon.com 13 | yahoo=https://www.yahoo.com 14 | bing=https://www.bing.com 15 | apple=https://www.apple.com 16 | microsoft=https://www.microsoft.com 17 | cloudflare=https://www.cloudflare.com 18 | spotify=https://www.spotify.com 19 | netflix=https://www.netflix.com 20 | dropbox=https://www.dropbox.com 21 | --------------------------------------------------------------------------------