AS43996 Booking.com BV 🇳🇱 NL
Announcing 21 prefixes, seen at the RIS collectors.
IPv4 prefixes
14
4,864 (19 × /24)
IPv6 prefixes
7
4,102 × /48
Upstreams
5
transit providers observed
Peers
10
settlement-free adjacencies
Downstreams
0
transit customers observed
Customer cone
0
ASes reachable through it
Registry and operator data
- AS number
- AS43996
- Name
- Booking.com BV
- Organisation
- Booking.com
- Country
- 🇳🇱 NL
- RIR
- RIPENCC
- Allocated
- 2007-10-31
- Network type
- Content
- Scope
- Global
- Peering policy
- Open
- IRR as-set
- AS-BOOKING
- Website
- https://www.booking.com
- PeeringDB
- net/5320
- Exchanges
- 7
- Facilities
- 3
RPKI coverage of this AS
Its own announcements, validated against the current ROA set
Upstreams
Networks seen providing transit to this one
| Network | Country | Cone | IPv4 prefixes | Paths | Source |
|---|---|---|---|---|---|
| AS3356 Lumen (Level 3) | 🇺🇸 US | 71,317 | 2,086 | 136 | CAIDA |
| AS6939 Hurricane Electric LLC | 🇺🇸 US | 54,042 | 185 | 158 | CAIDA |
| AS6461 Zayo Bandwidth | 🇺🇸 US | 53,494 | 212 | 173 | CAIDA |
| AS6762 Telecom Italia Sparkle (Seabone) | 🇮🇹 IT | 52,705 | 288 | 105 | CAIDA |
| AS3320 Deutsche Telekom AG | 🇩🇪 DE | 51,597 | 910 | 81 | CAIDA |
Peers
Adjacencies that look settlement-free rather than transit
| Network | Country | Cone | IPv4 prefixes | Paths | Source |
|---|---|---|---|---|---|
| AS9002 RETN Limited | 🇬🇧 GB | 51,811 | 18 | 59 | CAIDA |
| AS33891 Core-Backbone GmbH | 🇩🇪 DE | 26,879 | 1 | 19 | CAIDA |
| AS12389 Rostelecom PJSC | 🇷🇺 RU | 26,795 | 3,255 | 12 | CAIDA |
| AS3216 Vimpelcom PJSC | 🇷🇺 RU | 24,952 | 590 | 1 | CAIDA |
| AS20562 Open Peering (Broadband Hosting B.V.) | 🇳🇱 NL | 23,799 | 0 | 1 | CAIDA |
| AS9304 HGC Global Communications Limited | ðŸ‡ðŸ‡° HK | 6,277 | 2,168 | 9 | CAIDA |
| AS8218 Zayo Europe | 🇫🇷 FR | 341 | 19 | 13 | CAIDA |
| AS13030 Init7 (Switzerland) Ltd. | 🇨🇠CH | 329 | 69 | 6 | CAIDA |
| AS1836 green.ch AG | 🇨🇠CH | 45 | 78 | 19 | CAIDA |
| AS50304 Blix Solutions AS | 🇳🇴 NO | 34 | 103 | 32 | CAIDA |
Downstreams
Networks this one appears to provide transit to
No downstreams observed at the collectors.
Relationships marked inferred come from where the two networks sit on the AS paths the collectors see, which is a guess and is wrong for some of them. The rest are stated by CAIDA's published inference over a much wider set of collectors.