DMC · Peering
PEERING

AS268551

DMC Telecombilateral · open · direct
ASNAS268551
Peering policyOpen

Open a BGP session with DMC in minutes. IPs, filters, and communities — public, direct, no middlemen.

20–50 GbpsOpen PeeringBilateralIPv6RPKIIRR
OVERVIEW

The network

Brazilian operation since 2015. Direct edge at IX.br São Paulo — no resale, no middlemen, no ratio requirements.

ASN
AS268551
Policy
Open
Traffic
20–50 Gbps
Direction
Mostly Inbound
IRR as-set
AS268551:AS-CONE
Scope
South America
Protocols
IPv4 · IPv6 unicast
RIR
LACNIC · OK
CAPABILITIES

What we support

Full stack for technical interconnection. Everything other Tier-1 operators expect, with extras on request.

IPv4 unicast
IPv6 unicast
RPKI ROV — invalids dropped
IRR filtering (as-set)
Bilateral sessions
Via IX.br route servers
GTSM (TTL=255)
MD5 on request
BFD on request
BGP SESSION

Peering addresses

Bilateral and route-server sessions at IX.br São Paulo. For meaningful traffic we prefer bilateral; via the route servers, exchange starts with no extra configuration.

IX.br (PTT.br) São Paulo · #1
Port: 40G
IPv4
187.16.219.76
IPv6
2001:12f8::219:76
IX.br (PTT.br) São Paulo · #2
Port: 10G
IPv4
187.16.222.92
IPv6
2001:12f8::222:92
ASN
AS268551
IRR as-set
AS268551:AS-CONE

We already announce on the IX.br São Paulo route servers — if your network is on them too, traffic is already exchanged. For a bilateral session (recommended above a few Gbps), use the addresses above.

REQUIREMENTS

How to open a session

The parameters below cover what we need from your side and what we offer from ours. Fine details are aligned during activation.

Identification

  • ASN and legal name
  • IPv4 and IPv6 addresses for your IX.br SP session
  • Registered and up-to-date IRR / as-set
  • 24/7 NOC and technical (BGP) contacts

Policy & filters

  • Announce only your own prefixes and direct customers
  • IRR-based filtering (as-set) with periodic validation
  • RPKI mandatory — invalid ROA announcements are dropped
  • Prefixes more specific than /24 (IPv4) and /48 (IPv6) are not accepted

Limits & security

  • IPv4 max-prefix: 100 (negotiable per cone size)
  • IPv6 max-prefix: 50 (negotiable per cone size)
  • GTSM (TTL=255) recommended
  • MD5 and BFD available on request
PRESENCE

Interconnection points

Three interconnection environments in São Paulo. All support IPv4 and IPv6.

IX.br (PTT.br) São Paulo
São Paulo, BR
Equinix SP4
Barueri, BR
PIX Telium
São Paulo, BR
EXTERNAL VALIDATION

Verify the network

DMC Telecom operations are traceable on every public peering database.

RPKI — ROA coverage21 of 21 announced prefixes validMeasured on 2026-09-18 at RIPEstat, prefix by prefix — including the IPv6 more-specifics.
HOW TO REQUEST PEERING

Three paths, same answer

Pick the channel that fits your workflow. The form is the fastest path — it goes straight to the peering team.

01Recommended

Web form

Your request goes straight to the peering team. Reply during business hours.

02Traditional

Direct email

Send your ASN, IPs (v4/v6), as-set, and expected max-prefix. The peering team replies during business hours.

03Industry standard

PeeringDB

Use the PeeringDB request flow. Automatic social validation — we check our official profile.

CONTACT

Request peering

Send your ASN, IPs (IPv4/IPv6), as-set, and expected max-prefix. We reply during business hours. For active session incidents, use the 24/7 NOC.