AS274672 Peering Policy
Inovanoc Solucoes em Suporte · Netwiz · updated 2026-10-09
Summary
| ASN | AS274672 |
| Policy | Open |
| Contract | Not required |
| Traffic ratio | Not required |
| Multiple locations | Not required |
| IRR as-set | ALTDB::AS274672:AS-CUSTOMERS |
| MD5 / BFD | Preferred, not required |
| Recommended max-prefix | IPv4: 10 · IPv6: 20 |
| PeeringDB | peeringdb.com/asn/274672 |
| Looking Glass | lg.netwiz.com.br/lg |
| Geofeed | geofeed.inovanoc.com.br/geofeed.csv |
| Peering, NOC and abuse | suporte@inovanoc.com.br |
Our network
- IPv6:
2804:91e0::/32, announced as /40 blocks, each through its own upstream. Ten /40 blocks are designated to partner ISPs; seewhois.registro.brfor the responsible party of each block. - IPv4:
177.12.132.0/24,177.12.142.0/23,189.89.245.0/24. - Every announced prefix has a route/route6 object in ALTDB and a matching RPKI ROA.
Requirements for peers
- Public ASN and an up-to-date PeeringDB record.
- Routes registered in an IRR and grouped in an as-set (or aut-num) that we can use to build filters.
- No RPKI-invalid routes, bogon prefixes or private ASNs in announcements.
- Announce only your own routes and your customers' routes; never routes learned from upstreams or other peers.
- A reachable technical contact for operational issues.
How to request peering
Send an e-mail to suporte@inovanoc.com.br with your ASN, as-set, the location or IX, the IPv4/IPv6 addresses for the session and your technical contact. We prefer sessions with MD5 authentication and BFD; tell us if you can enable them.
Resumo em portugues
Politica aberta: fazemos peering com qualquer rede que cumpra os requisitos acima, sem contrato, sem exigencia de proporcao de trafego e sem minimo de localidades. MD5 e BFD sao preferidos, mas nao obrigatorios. Pedidos para suporte@inovanoc.com.br com ASN, as-set, local/IX, enderecos da sessao e contato tecnico.