ixreport

Serbia BroadBand

AS31042 · Yettel

Serbia BroadBand d.o.o.

4Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
NSPType
OpenPeering policy
2Using the route servers
3To fix in PeeringDB
0Facilities in PeeringDB

Tools: Where can I peer with Serbia BroadBand? · Where should Serbia BroadBand peer next? · Compare Serbia BroadBand with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

3 things to fix in Serbia BroadBand's PeeringDB record, from what its exchanges publish: 2 to add, 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Serbia BroadBand's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (2)

On the exchange's own member list, but not in Serbia BroadBand's PeeringDB record. Add one entry per connection with these values.

  1. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Hungary BIX Budapest, Hungary · PeeringDB 55From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB80.81.193.203 is AS31638 Lepida80.81.193.203
    IPv4 address missing from PeeringDBnone80.81.193.25 80.81.193.203
    IPv6 address missing from PeeringDB2001:7f8::3e56:0:22001:7f8::3e56:0:2 2001:7f8::7942:0:2
    Port speed differs50G300G + 100G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • In the entry with IPv6 2001:7f8::3e56:0:2: set Speed to 100000 (100G) (now 50000).
    • Add an entry: IPv4 80.81.193.25, IPv6 2001:7f8::7942:0:2, speed 300000 (300G), RS peer yes.

Exchanges over time

01234Oct 3, 2026Nov 19, 20264
Show as a table
DateExchanges
Nov 19, 20264
Nov 18, 20264
Nov 17, 20264
Nov 16, 20264
Nov 15, 20264
Nov 14, 20264
Nov 13, 20264
Nov 12, 20264
Nov 11, 20264
Nov 10, 20264
Nov 9, 20264
Nov 8, 20264
Nov 7, 20264
Nov 6, 20264
Nov 5, 20264
Nov 4, 20264
Nov 3, 20264
Nov 2, 20264
Nov 1, 20264
Oct 31, 20264
Oct 30, 20264
Oct 29, 20264
Oct 28, 20264
Oct 27, 20264
Oct 26, 20264
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Serbia BroadBand's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 450G, at the 2 of 4 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Bulgaria B-IX Sofia, Bulgaria Website list only
Hungary BIX Budapest, Hungary Website list only
Germany DE-CIX Frankfurt Frankfurt, Germany 2001:7f8::3e56:0:2 50G 248 routes Both Address takenIPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Serbia SOX Serbia Belgrade/Serbia, Serbia 185.1.27.37
185.1.27.57
2 × 200G Yes PeeringDB

Serbia BroadBand lists no facilities in PeeringDB.

Recent changes Search them

  • Oct 19, 2026 [PDB] AS31042 Serbia BroadBand now in PeeringDB at DE-CIX Frankfurt