Is First Bank of Nigeria down in Nigeria?

We can't tell right now whether First Bank of Nigeria works

People: 0 reports in the last hour Official page: No public status page Our checks: responded from 0 of 35 places
What this means
We can't tell yet whether the First Bank of Nigeria server responds. Updated 10 Nov, 20:05 UTC, 11 min ago · Website checks: these do not test every feature A response from the server does not confirm that sign-in, payments, messaging or the app is working.
Report a problem
Change country

No connected status feed

We don't read an official status source for First Bank of Nigeria, so no provider incidents or maintenance are shown here.

Our checks show whether firstbanknigeria.com responds. Any answer counts, even an error page. These checks do not test every feature.

Reports from people

Last 24 hours · Worldwide · times in UTC

0 reports

No community reports in the last 24 hours. Having trouble? Add your report.

024 00:0006:0012:0018:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 10 Nov, 20:16 UTC

Report a problem with First Bank of Nigeria

Tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour from each network. This adds your experience to the chart; the provider is not contacted.

Where this status comes from

Website checks

Our own checks of firstbanknigeria.com

Every 5 minutes, from our probes

None of 35 cities can reach firstbanknigeria.com.

Portsmouth: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Melbourne: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) São Paulo: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Osaka: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Tokyo: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Toronto: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Johannesburg: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Bangalore: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) St. Louis: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Madrid: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Doha: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Lauterbourg: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Jakarta: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Mumbai: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Singapore: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Seattle: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) New Jersey: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Warsaw: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Frankfurt: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Amsterdam: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Tel Aviv: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Atlanta: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Hamina: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Cape Town: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Seoul: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Delhi: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) New York: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Port Louis: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Hong Kong: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Querétaro: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Dallas: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) London: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Los Angeles: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Santiago: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c) Sydney: could not load it (SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] c)
  • PortsmouthCertificate not trusted22 ms, just now
  • MelbourneCertificate not trusted546 ms, just now
  • São PauloCertificate not trusted402 ms, just now
  • OsakaCertificate not trusted492 ms, just now
  • TokyoCertificate not trusted467 ms, just now
  • TorontoCertificate not trusted179 ms, just now
  • JohannesburgCertificate not trusted346 ms, just now
  • BangaloreCertificate not trusted270 ms, just now
  • St. LouisCertificate not trusted205 ms, 1 min ago
  • MadridCertificate not trusted51 ms, 1 min ago
  • DohaCertificate not trusted311 ms, 1 min ago
  • LauterbourgCertificate not trusted71 ms, 1 min ago
  • JakartaCertificate not trusted501 ms, 1 min ago
  • MumbaiCertificate not trusted266 ms, 1 min ago
  • SingaporeCertificate not trusted326 ms, 1 min ago
  • SeattleCertificate not trusted314 ms, 1 min ago
  • New JerseyCertificate not trusted819 ms, 1 min ago
  • WarsawCertificate not trusted72 ms, 1 min ago
  • FrankfurtCertificate not trusted40 ms, 1 min ago
  • AmsterdamCertificate not trusted25 ms, 1 min ago
  • Tel AvivCertificate not trusted140 ms, 1 min ago
  • AtlantaCertificate not trusted196 ms, 1 min ago
  • HaminaCertificate not trusted109 ms, 2 min ago
  • Cape TownCertificate not trusted459 ms, 2 min ago
  • SeoulCertificate not trusted501 ms, 2 min ago
  • DelhiCertificate not trusted540 ms, 7 min ago
  • New YorkCertificate not trusted155 ms, 7 min ago
  • Port LouisCertificate not trusted717 ms, 7 min ago
  • Hong KongCertificate not trusted491 ms, 7 min ago
  • QuerétaroCertificate not trusted268 ms, 7 min ago
  • DallasCertificate not trusted318 ms, 7 min ago
  • LondonCertificate not trusted11 ms, 8 min ago
  • Los AngelesCertificate not trusted398 ms, 8 min ago
  • SantiagoCertificate not trusted390 ms, 8 min ago
  • SydneyCertificate not trusted514 ms, 8 min ago

We request firstbanknigeria.com and note whether it answers. These automated checks do not sign in or use the app's features.

Available evidence

We check whether its server responds every 5 minutes (any answer counts, even an error page). This does not test sign-in, payments, calls or every feature of its app or network. We show a website problem when a quarter of the eligible places cannot load it, and an outage when half cannot. Places that normally cannot reach it are excluded. With too few results, we say we cannot tell.

Outage history

Last 9030 days

History starts with our first reading

Of the last 90 days, 0 had a partial or major outage, 0 had maintenance only and 90 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Recent problems

No history yet. It starts with our first reading of the website.

What can I try?

Having trouble with First Bank of Nigeria?

  1. Compare reports and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Questions about these results

Questions

Is First Bank of Nigeria down, or is it just me?

We can't say yet: see the line at the top.

How do we know?

First Bank of Nigeria has no public status page that we know of, so there is no official status to show here. We load firstbanknigeria.com from our servers in several cities and note whether DNS, the secure connection and the page respond. That does not test sign-in, payments or the app. People can report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

The website every 5 minutes, day and night. We keep 90 days of available check history: a day we have no reading for shows as "no data yet", never as working.

Other services in Finance and accounting

Each card shows that service's own status, not First Bank of Nigeria's. A problem listed here does not mean First Bank of Nigeria has one.

See the live outage feed · Find another service