Is redbus.pro down or not working?

What happened to redbus.pro, why did the website go down and not work? Here you can see who else is having the same problem with redbus.pro, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, redbus.pro is working fine, but single failures are possible. If redbus.pro does not work for you, then report your problem and write a comment.

Add comment

What to do if the site redbus.pro is not available? Try our guide.

redbus.pro outage reports in the last 24 hours

redbus.pro - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.

No registration required.
Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
Active links in the text of the message are not published, but displayed in plain text.
It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Your name:

Message:

Technical information

Main page title:

redPro Win

Main page description:

just another react + webpack boilerplate

Protocol:

https

Status code:

200

Page size:

3.5 KB

Response time:

1.543sec.

IP:

18.140.220.24

Response headers:

content-type:	text/html; charset=utf-8
server:	nginx/1.24.0 (Ubuntu)
x-powered-by:	Express
cache-control:	private, no-cache, no-store, must-revalidate
expires:	-1
pragma:	no-cache
etag:	W/"e0a-jlpZG8jvwUUQIEAFJFkPfGEj87c"
date:	Sun, 06 Oct 2024 22:55:29 GMT
content-length:	3594
connection:	close
alt-svc:	h3=":443"; ma=93600
strict-transport-security:	max-age=15768000 ; includeSubDomains ; preload

DNS records:

A	address	54.254.252.236
A	ttl	60
A	address	18.140.220.24
A	ttl	60
MX	exchange	alt1.aspmx.l.google.com
MX	priority	5
MX	exchange	alt2.aspmx.l.google.com
MX	priority	5
MX	exchange	alt4.aspmx.l.google.com
MX	priority	10
MX	exchange	aspmx.l.google.com
MX	priority	1
MX	exchange	alt3.aspmx.l.google.com
MX	priority	10
NS	value	ns-199.awsdns-24.com
NS	value	ns-1437.awsdns-51.org
NS	value	ns-1777.awsdns-30.co.uk
NS	value	ns-728.awsdns-27.net
TXT	entries	google-site-verification=7ebzROpZlvMl4AM5AvcR_X9o7e7aZWH-5uSxhtPjTXw
SOA	nsname	ns-1777.awsdns-30.co.uk
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400

How to solve problems with redbus.pro

Errors on the redbus.pro website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of redbus.pro on your own.