Autonomous system
AS18255 BRISBANE-AP Brisbane City Council
Unclassified APNIC
Summary
Brisbane City Council
government municipal network australia
The AS handle BRISBANE-AP is held by Brisbane City Council.
What it's used for
- The address space carries municipal infrastructure, evidenced by netnames
BCC-APandBRISBANECITYCOU-AUregistered toIRT-BCC-AU. - The AS announces 1280 IPv4 addresses across 4 prefixes, with 6 observed neighbours, indicating a small-scale internal network rather than a transit or large access provider.
Notable
- All registrants align with the announcer, consistently identifying
Brisbane City Councilas the owner. - The inventory consists of four distinct IPv4 blocks, including a /23 and three /24s, all located in Australia.
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
Recorded at 3 exchanges in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| Megaport IX Sydney | Sydney, Australia | 103.26.69.47 |
| Megaport IX Melbourne | Melbourne, Australia | 103.26.71.110 |
| Megaport IX Brisbane | Brisbane, Australia | 103.26.70.72 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 1.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| AU | Australia | 4 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS18255- Registry name
- BRISBANE-AP
- Registrant
- Brisbane City Council
- Abuse contact
- hostmaster@brisbane.qld.gov.au
- Registered
- 2008-09-04
- Last changed
- 2020-05-26
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Brisbane City Council
- Also known as
- BCC
- Scope
- Australia
- Traffic ratio
- Not Disclosed
- Peering policy
- Restrictive
- Present at
- 3 exchanges
- Website
- http://www.brisbane.qld.gov.au
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
- 100% valid · 5 valid, 0 with no ROA
- ROAs
- 5 authorising AS18255
- ASPA
- no ASPA record
- IRR
- 100% registered · 5 of 5 announcements
- Route objects
- 11 naming AS18255
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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