iCampPro Outage History

iCampPro is up right now

iCampPro had 7 outages in the last 2 years totaling 26h 34m of downtime — averaging 0.3 incidents per month.

There were 7 iCampPro outages since August 15, 2024 totaling 26h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.icamppro.com

Notice September 27, 2025

Brief Outage

Detected by Pingoru
Sep 27, 2025, 05:27 PM UTC
Resolved
Sep 27, 2025, 05:27 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 27, 2025, 05:27 PM UTC

    On September 26, from 3:45 PM to 4:44 PM (CT), one of our third-party processing partners experienced an issue that may have affected some iCampPro customers' ability to accept payments. We apologize for any inconvenience this may have caused. Our partner has confirmed that the issue has been fully resolved. We continue to work closely with them to monitor performance and ensure everything is working as intended.

Read the full incident report →

Minor April 24, 2025

Issue with Secure Payments

Detected by Pingoru
Apr 24, 2025, 02:11 PM UTC
Resolved
Apr 24, 2025, 02:19 PM UTC
Duration
7m
Affected: iCampPro Payments
Timeline · 2 updates
  1. investigating Apr 24, 2025, 02:11 PM UTC

    We are currently experiencing an issue with our secure payment form that may temporarily prevent payment processing. Our team is actively working to resolve the issue. We will provide additional updates as progress continues.

  2. resolved Apr 24, 2025, 02:19 PM UTC

    On April 24, from 8:49 AM to 9:11 AM, the secure payment form experienced a brief interruption. The issue has been fully resolved, and we will continue monitoring to ensure everything is working as intended.

Read the full incident report →

Notice April 3, 2025

Settlement Update

Detected by Pingoru
Apr 03, 2025, 06:17 PM UTC
Resolved
Apr 03, 2025, 06:17 PM UTC
Duration
Affected: iCampPro Payments
Timeline · 1 update
  1. resolved Apr 03, 2025, 06:17 PM UTC

    We identified an issue that led to partial payouts for some accounts related to the deposit scheduled for April 3. To resolve this, a same-day ACH transfer was initiated this morning. The remaining funds from April 1, along with those from April 2, will be deposited by the end of the day. You should have already received your Settlement Summary, and the transfer details are available for review in the merchant portal. If you have any questions or need additional assistance, please don’t hesitate to reach out to our payments team at 1.877.554.6776 (option 4) or via email at [email protected].

Read the full incident report →

Notice April 1, 2025

Delay Settlement

Detected by Pingoru
Apr 01, 2025, 08:38 PM UTC
Resolved
Apr 02, 2025, 08:21 PM UTC
Duration
23h 42m
Affected: iCampPro Payments
Timeline · 2 updates
  1. monitoring Apr 01, 2025, 08:38 PM UTC

    Please be advised that on March 31, one of our third party partners experienced a settlement delay for a subset of accounts. As a result, we will be attempting to process the transfer as same day ACH to ensure you receive the deposit by the end of the day on April 2, as scheduled, to minimize any impact. Additionally, these transfers will include all transactions from both March 31 and April 1, with April 1 transactions being deposited one day earlier than expected.

  2. resolved Apr 02, 2025, 08:21 PM UTC

    All transfers have been successfully initiated. Please note that same day ACH submission for standard funding was not possible, and deposits will be received on 4/3. You can view your transfer details by logging into merchantportal.iclasspro.com. If you have any further questions, feel free to reach out to our payments support team at 1.877.554.6776 (Option 4) or via email at [email protected].

Read the full incident report →

Notice March 31, 2025

Connectivity Issues

Detected by Pingoru
Mar 31, 2025, 09:29 PM UTC
Resolved
Mar 31, 2025, 09:29 PM UTC
Duration
Affected: iCampPro Payments
Timeline · 1 update
  1. resolved Mar 31, 2025, 09:29 PM UTC

    On March 31, one of our third party partners experienced brief connectivity issues from 1:33 to 1:34 PM CT and again from 1:43 to 1:44 PM CT. These intermittent disruptions may have affected payment processing. Please retry any failed transactions, as our partner has confirmed the issue was fully resolved.

Read the full incident report →

Minor March 27, 2025

Payments Settlement Issue

Detected by Pingoru
Mar 27, 2025, 01:49 PM UTC
Resolved
Mar 27, 2025, 04:33 PM UTC
Duration
2h 44m
Affected: iCampPro Payments3rd Party Integration/Provider
Timeline · 3 updates
  1. monitoring Mar 27, 2025, 01:49 PM UTC

    One of our third-party partners experienced a delayed settlement on 3/25, which caused the settlement to process on 3/26, potentially resulting in a 1-day delay in receiving deposits. We apologize for this inconvenience and anticipate all transfer schedules to resume as expected. Thank you for your understanding and patience.

  2. monitoring Mar 27, 2025, 04:33 PM UTC

    The team successfully expedited the funding process and arranged a same day deposit, so your funds will still be deposited today (3/27) as expected, before the bank closes. If you need further assistance, please don't hesitate to contact our Payments Support team directly at [email protected] or by phone at 1.877.554.6776 (Option 4). Thank you!

  3. resolved Mar 27, 2025, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 15, 2024

Issues With Integrated Terminal Functionality

Detected by Pingoru
Aug 15, 2024, 08:14 PM UTC
Resolved
Aug 15, 2024, 08:14 PM UTC
Duration
Affected: iCampPro Payments3rd Party Integration/Provider
Timeline · 1 update
  1. resolved Aug 15, 2024, 08:14 PM UTC

    On August 15, 2024 from 9:41 am (CT) - 12:34 pm (CT), some transactions made using an integrated terminal with iClassPro/iCampPro may have been declined due to an issue with a third party processing partner. The problem has since been resolved and we will continue to monitor the application to ensure it is behaving properly. Those impacted may need to restart their devices in order to reconnect successfully. Thank you.

Read the full incident report →