Autonomous system
AS33583 IBC-FGIS
Unclassified ARIN Enterprise
Summary
Isabella Bank Corporation
banking enterprise us financial
The AS handle IBC-FGIS is held by Isabella Bank Corporation.
What it's used for
- The address space carries the internal network infrastructure for a financial services holding company, as indicated by the registrant name and netname
IBC-FGIS. - The inventory consists of 768 IPv4 addresses across 2 prefixes, with 2 observed neighbours, implying a small, self-contained enterprise network rather than a transit or access provider.
Notable
- The registrants for both announced prefixes,
199.30.148.0/23and199.30.150.0/24, are listed as Isabella Bank Corporation, matching the AS holder. - The address inventory is finely subdivided into two small blocks, consistent with an internal corporate estate segmented for specific site or departmental use.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-19, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 768 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 2 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS33583- Registry name
- IBC-FGIS
- Registrant
- Isabella Bank Corporation
- Abuse contact
- ITServices@isabellabank.com
- Registered
- 2010-10-04
- Last changed
- 2012-02-24
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- IBC-FGIS
- Network type
- Enterprise
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Selective
- Website
- https://isabellabank.com
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 3 with no ROA
- ROAs
- 0 authorising AS33583
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 4 naming AS33583
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,783 prefixes, as published 2026-10-20. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere