DMC · Peering
PEERING

AS268551

DMC Telecom
bilateral · open · direct

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 · Multicast
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
IPv6 Multicast
RPKI ROV — invalids dropped
IRR filtering (as-set)
Bilateral only (no route servers)
GTSM (TTL=255)
MD5 / TCP-AO on request
BFD on request
BGP Communities (informational + action)
BGP SESSION

Peering addresses

Bilateral sessions at IX.br São Paulo. We do not announce via route servers — all sessions are established directly.

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

DMC Telecom does not establish sessions via route servers. All sessions are bilateral.

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
COMMUNITIES

BGP Communities

Informational communities mark prefix origin and location. Action communities let peers control propagation.

Informational
Community
Description
268551:1000
Aprendido em IX.br SP
268551:1100
Aprendido em Equinix SP2
268551:1200
Aprendido em PIX Telium
268551:2000
Aprendido de cliente
268551:3000
Aprendido de peer
268551:4000
Aprendido de upstream
Action
Community
Description
0:268551
Não anunciar (no-export por DMC)
268551:666
Blackhole (RFC 7999)
268551:6500
Não anunciar para upstreams
268551:6510
Prepend 1x para upstreams
268551:6520
Prepend 2x para upstreams
268551:6530
Prepend 3x para upstreams

List under review. Confirm with the peering team before production use.

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 SP2
Barueri, BR
PIX Telium
São Paulo, BR
EXTERNAL VALIDATION

Verify the network

DMC Telecom operations are traceable on every public peering database.

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.