Routing security
AS41765 IPGARDE-AS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS41765 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0c:d500::/29 | RPKI valid | IRR | 31 |
| 2a02:2288::/29 | RPKI valid | IRR | 31 |
| 31.172.164.0/22 | RPKI valid | IRR | 52 |
| 45.8.233.0/24 | RPKI valid | IRR | 51 |
| 45.8.234.0/24 | RPKI valid | IRR | 52 |
| 45.8.235.0/24 | RPKI valid | IRR | 52 |
| 82.138.64.0/23 | RPKI valid | IRR | 52 |
| 185.4.63.0/24 | RPKI valid | IRR | 52 |
| 185.84.112.0/22 | RPKI valid | IRR | 52 |
| 185.233.48.0/24 | RPKI valid | IRR | 52 |
| 188.65.168.0/21 | RPKI valid | IRR | 52 |
| 193.33.46.0/23 | RPKI valid | IRR | 52 |
| 193.37.150.0/24 | RPKI valid | IRR | 52 |
| 193.57.96.0/24 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS41765 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 31.172.164.0/22 | /22 | RIPENCC |
| 45.8.233.0/24 | /24 | RIPENCC |
| 45.8.234.0/24 | /24 | RIPENCC |
| 45.8.235.0/24 | /24 | RIPENCC |
| 82.138.64.0/23 | /23 | RIPENCC |
| 185.4.63.0/24 | /24 | RIPENCC |
| 185.84.112.0/22 | /22 | RIPENCC |
| 185.233.48.0/22 | /22 | RIPENCC |
| 185.233.48.0/24 | /24 | RIPENCC |
| 185.233.48.10/32 | /32 | RIPENCC |
| 185.233.50.0/23 | /23 | RIPENCC |
| 188.65.168.0/21 | /21 | RIPENCC |
| 193.33.46.0/23 | /23 | RIPENCC |
| 193.37.150.0/24 | /24 | RIPENCC |
| 193.57.96.0/24 | /24 | RIPENCC |
| 2a02:2288::/29 | /29 | RIPENCC |
| 2a02:2288::/32 | /32 | RIPENCC |
| 2a0c:d500::/29 | /29 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS174 | Cogent Communications, LLC | Declared | Observed |
| AS3356 | Level 3 Parent, LLC | Declared | Observed |
| AS8218 | Zayo Infrastructure France SA | Declared | Observed |
| AS29075 | IELO-LIAZO SERVICES SAS | Declared | Observed |
| AS30781 | Free Pro SAS | Declared | Observed |
| AS204092 | Association GRIFON | not declared | Observed |
| AS6696 | VERIXI SA | not declared | Observed |
| AS35661 | VIRTUA SYSTEMS SAS | not declared | Observed |
| AS34927 | iFog GmbH | not declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS41765 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 185.233.48.0/22 | RIPE | — | MNT-IPGARDE | 2019-11-25 | Not announced |
| 185.233.50.0/23 | RIPE | — | MNT-IPGARDE | 2021-08-16 | Not announced |
| 2a02:2288::/32 | RIPE | IP Garde | MNT-IPGARDE | 2015-07-02 | Not announced |
| 31.172.164.0/22 | RIPE | IPGARDE | MNT-IPGARDE | 2012-10-08 | Announced |
| 45.8.233.0/24 | RIPE | — | MNT-IPGARDE | 2025-02-07 | Announced |
| 45.8.234.0/24 | RIPE | — | MNT-IPGARDE | 2023-01-09 | Announced |
| 45.8.235.0/24 | RIPE | — | MNT-IPGARDE | 2023-01-09 | Announced |
| 82.138.64.0/23 | RIPE | IPGarde | COGENT-ROUTE-MNT | 2007-01-22 | Announced |
| 185.4.63.0/24 | RIPE | IPGARDE | MNT-IPGARDE | 2014-09-12 | Announced |
| 185.84.112.0/22 | RIPE | — | MNT-IPGARDE | 2023-12-21 | Announced |
| 185.233.48.0/24 | RIPE | — | MNT-IPGARDE | 2020-11-03 | Announced |
| 188.65.168.0/21 | RIPE | — | MNT-IPGARDE | 2010-05-04 | Announced |
| 193.33.46.0/23 | RIPE | IPGarde | MNT-IPGARDE | 2021-11-12 | Announced |
| 193.37.150.0/24 | RIPE | IP Garde | MNT-IPGARDE | 2021-11-12 | Announced |
| 193.57.96.0/24 | RIPE | — | MNT-IPGARDE | 2023-10-26 | Announced |
| 2a02:2288::/29 | RIPE | — | MNT-IPGARDE | 2021-08-20 | Announced |
| 2a0c:d500::/29 | RIPE | — | MNT-IPGARDE | 2019-11-25 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS41765 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-IPGARDE-CUST | RIPE | Lists AS41765 as a direct member |
AS-PHIBEE-TELECOM | RIPE | Lists AS41765 as a direct member |
AS-PHIBEE-TELECOM-IPV6 | RIPE | Lists AS41765 as a direct member |
AS29075:AS-CUSTOMERS | RIPE | Lists AS41765 as a direct member |
AS8218:AS-CUSTOMERS | RIPE | Lists AS41765 as a direct member |
RPKI from rpki-client, validated 2026-10-15 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-15. Cross-check on bgp.he.net.