Singapore servers, what happened?

[thaigrr 0]

Hello Guys,

 I've been an satisfied AirVPN client for over 10 years, this past month I've noticed that the Singapore servers which I mainly use now have a latency that's very poor (I'm in S.E Asia)
The Eddie client is showing that Japan is better for Latency so I connect to them.
While connecting to a few Singapore nodes I'm also noticing that my 1st, 2nd and 3rd hops are coming out of Romania.
vlan12.as06-10g.wco1.sg.m247.ro 
irb-1906.agg1v.wco1.sg.m247.ro
be-2-3111.bb1n.wco1.sg.m247.ro

While that would explain the latency issue if I'm actually connecting to Romanian servers but I'm supposed to be using Singapore.
Hopefully someone can explain the issue I'm having.

Thanks

[Staff 10521]

Hello!

This message has been picked to experiment answers by a selected LLM. The answer has been verified manually and slightly edited. In short, the hops you mention are in Singapore. No changes in Singapore infrastructure took place to justify the change in latency you detect.

Operator: locate countries of: vlan12.as06-10g.wco1.sg.m247.ro irb-1906.agg1v.wco1.sg.m247.ro be-2-3111.bb1n.wco1.sg.m247.ro

 

All three hostnames point to infrastructure in Singapore.

Here’s how that breaks down:

• wco1.sg.m247.ro
  • sg is the standard country/location code for Singapore
  • wco1 likely refers to a specific data center or site within that region
  • m247.ro is a Romanian network provider (M247), but they operate globally

So for each:

• vlan12.as06-10g.wco1.sg.m247.ro → Singapore
• irb-1906.agg1v.wco1.sg.m247.ro → Singapore
• be-2-3111.bb1n.wco1.sg.m247.ro → Singapore

Summary:
All three are part of M247’s network presence in Singapore, despite the .ro domain.

 

Operator: Break down names with additional details

 

These hostnames follow fairly typical ISP / backbone naming conventions. Each segment encodes device role, interface, and location. Let’s break them down piece by piece.

---

🌍 Common suffix (applies to all)

• m247.ro → Network operated by M247 (Romanian-origin ISP with global PoPs)
• sg → Singapore
• wco1 → Likely “West Coast / core site 1” (internal site code for that Singapore PoP)

So all three are devices inside the same Singapore location.

---

1️⃣ vlan12.as06-10g.wco1.sg.m247.ro

Breakdown:

• vlan12
  • A VLAN interface (Virtual LAN ID 12)
  • Used for logical segmentation inside a router/switch
• as06-10g
  • as06 → likely “access switch / aggregation switch #6”
  • 10g → 10 Gigabit interface/uplink
• wco1.sg.m247.ro
  • Location + provider (Singapore PoP)

Interpretation:

👉 A VLAN interface (ID 12) on an access/aggregation switch with a 10G link
👉 Likely used for customer traffic or internal segmentation

---

2️⃣ irb-1906.agg1v.wco1.sg.m247.ro

Breakdown:

• irb-1906
  • IRB = Integrated Routing and Bridging
  • Interface number 1906
  • Common on Juniper gear (Layer 3 gateway for a VLAN)
• agg1v
  • agg → aggregation router/switch
  • 1 → device number
  • v → possibly “virtualized” or variant of the node
• wco1.sg.m247.ro
  • Same Singapore site

Interpretation:

👉 A Layer 3 gateway interface (IRB) on an aggregation router
👉 Handles routing between VLANs or customer subnets

---

3️⃣ be-2-3111.bb1n.wco1.sg.m247.ro

Breakdown:

• be-2-3111
  • BE = Bundle Ethernet (port-channel / LAG)
  • 2 → bundle ID
  • 3111 → internal interface identifier
• bb1n
  • bb → backbone router
  • 1 → device number
  • n → possibly “north” (directional naming is common)
• wco1.sg.m247.ro
  • Same location

Interpretation:

👉 A backbone router interface using a bundled (aggregated) high-capacity link
👉 Likely part of core transit or inter-PoP connectivity

---

🧠 Big picture (network hierarchy)

Putting them together:

• Access layer → as06-10g (customer-facing / edge connectivity)
• Aggregation layer → agg1v (traffic consolidation + routing)
• Backbone/core layer → bb1n (high-capacity transit)

This is a classic ISP architecture:

 

Customer VLAN → Access Switch → Aggregation Router → Backbone Router

 

---

⚠️ Important note

These interpretations are informed guesses, not guaranteed facts. Naming conventions vary by provider, but M247’s style aligns closely with standard ISP practices.

Kind regards